Wiki source code of TrackerD -LoRaWAN Tracker User Manual

Version 84.2 by Xiaoling on 2022/10/24 10:58

version	line-number	content
51.2	1	(% style="text-align:center" %)
	2	[[image:1664505654417-133.png]]
	3
	4
	5
	6
7.1	7	(% class="wikigeneratedid" %)
	8	Table of Contents:
1.1	9
51.2	10	{{toc/}}
1.1	11
2.1	12
	13
12.1	14
15.2	15	= 1. Introduction =
	16
	17
50.2	18	== 1.1 What is TrackerD ==
15.2	19
50.2	20
15.3	21	(((
	22	TrackerD is an (% style="color:blue" %)Open Source LoRaWAN Tracker(%%) based on (% style="color:blue" %)ESP32 MCU(%%) and (% style="color:blue" %)Semtech LoRa Wireless Chip.
	23	)))
7.2	24
15.3	25	(((
19.2	26	In TrackerD, there are various sensors such as GPS, WiFi, BLE, Temperature, Humidity, Motion Detection, and Buzzer. User can use TrackerD for different tracking scenario.
7.2	27
51.18	28	(((
8.1	29	TrackerD is program friendly. Developers can use Arduino IDE to customize the software of TrackerD to fit their IoT solution.
51.18	30	)))
8.1	31
51.18	32	(((
19.2	33	The LoRa wireless technology used in TrackerD allows the user to send data and reach extremely long ranges at low data-rates. It provides ultra-long range spread spectrum communication and high interference immunity whilst minimizing current consumption. It targets professional tracking services.
15.3	34	)))
51.18	35	)))
8.1	36
15.3	37	(((
	38	TrackerD is equipped with a (% style="color:blue" %)1000mAh Li-on rechargeable battery(%%). Each TrackerD has a worldwide unique OTAA keys to join the LoRaWAN network.
16.4	39
	40
15.3	41	)))
8.1	42
19.2	43	[[image:1664499921684-770.png]]
8.1	44
15.4	45
19.2	46	(% style="color:red" %)Note: LoRaWAN server can be a general LoRaWAN server other than TTN.
8.1	47
15.2	48
50.2	49
19.2	50	== 1.2 Specifications ==
12.1	51
15.2	52
19.2	53	(% style="color:blue" %)Micro Controller:
15.2	54
19.2	55	* Espressif ESP32 PICO D4
	56	* MCU: ESP32 PICO D4
	57	* Bluetooth: Bluetooth V4.2 BR/EDR and Bluetooth LE
	58	* WiFi : 802.11 b/g/n (802.11n up to 150 Mbps)
	59	* Integrated SPI flash : 4 MB
	60	* RAM: 448 KB
	61	* EEPROM: 520 KB
	62	* Clock Speed: 32Mhz
	63
	64	(% style="color:blue" %)Common DC Characteristics:
	65
	66	* Supply Voltage: 5V via USB port or Internal li-on battery
	67	* Operating Temperature: -40 ~~ 60°C
	68
	69	(% style="color:blue" %)LoRa Spec:
	70
	71	* Frequency Range,
	72	** Band 1 (HF): 862 ~~ 1020 Mhz
	73	* 168 dB maximum link budget.
	74	* +20 dBm - 100 mW constant RF output vs.
	75	* +14 dBm high efficiency PA.
	76	* Programmable bit rate up to 300 kbps.
	77	* High sensitivity: down to -148 dBm.
	78	* Bullet-proof front end: IIP3 = -12.5 dBm.
	79	* Excellent blocking immunity.
	80	* Low RX current of 10.3 mA, 200 nA register retention.
	81	* Fully integrated synthesizer with a resolution of 61 Hz.
	82	* FSK, GFSK, MSK, GMSK, LoRaTM and OOK modulation.
	83	* Built-in bit synchronizer for clock recovery.
	84	* Preamble detection.
	85	* 127 dB Dynamic Range RSSI.
	86	* Automatic RF Sense and CAD with ultra-fast AFC.
	87	* Packet engine up to 256 bytes with CRC.
	88	* LoRaWAN 1.0.3 Specification
	89
	90	(% style="color:blue" %)Battery:
	91
	92	* 1000mA Li-on Battery power (for model TrackerD)
	93
	94	(% style="color:blue" %)Power Consumption
	95
	96	* Sleeping Mode: 200uA
	97	* LoRa Transmit Mode: 125mA @ 20dBm 44mA @ 14dBm
	98	* Tracking: max: 38mA
	99
84.2	100
	101
19.2	102	== 1.3 Features ==
	103
	104
	105	* LoRaWAN 1.0.3 Class A
	106	* ESP32 PICO D4
	107	* SX1276/78 Wireless Chip
51.31	108	* Arduino IDE Compatible
19.2	109	* Open source hardware / software
	110	* Regular/ Real-time GPS,BLE,WIFI tracking
	111	* Built-in3 axis accelerometer (LIS3DH)
	112	* Humidity / temperature sensor : GXCAS Technology GXHT3X
	113	* Motion sensing capability
	114	* Power Monitoring
	115	* Charging circuit via USB port
	116	* 1000mA Li-on Battery power
	117	* Tri-color LED, Alarm button
	118	* Datalog
	119
84.2	120
	121
19.2	122	== 1.4 Applications ==
	123
	124
12.1	125	* Logistics and Supply Chain Management
	126	* Human tracking
	127
84.2	128
	129
19.3	130	= 2.1 Use TrackerD =
19.2	131
50.2	132
19.3	133	== 2.1 How it works? ==
19.2	134
19.3	135
19.2	136	TrackerD is configured as LoRaWAN OTAA Class A GPS tracker by default. It has OTAA keys to join LoRaWAN network. To connect a LoRaWAN network, user need to input the OTAA keys in the LoRaWAN IoT server and push reset button of TrackerD (next to USB port). TrackerD will wake up and auto join the network via OTAA.
	137
	138
50.2	139
19.3	140	== 2.2 Quick guide to connect to LoRaWAN server ==
19.2	141
	142
50.2	143	Here is an example for how to join the [[TTNv3 LoRaWAN Network>>url:https://eu1.cloud.thethings.network]]. Below is the network structure, we use LPS8N as LoRaWAN gateway in this example.
19.2	144
	145
50.2	146	[[image:1664501652064-326.png]]
19.2	147
50.2	148
	149
19.2	150	The LPS8N is already set to connect to [[TTN V3 network >>url:https://eu1.cloud.thethings.network/]]. What the rest need to is register this device in TTN V3:
	151
	152
50.2	153	(% style="color:blue" %)Step 1:(%%) Create a device in TTN V3 with the OTAA keys from TrackerD.
	154
19.2	155	Each TrackerD is shipped with a sticker with the default device EUI as below:
	156
51.3	157
50.2	158	[[image:1664501677253-891.png]]
19.2	159
	160
	161	Input these keys to their LoRaWAN Server portal. Below is TTN V3 screen shot:
	162
	163
50.2	164	__Add APP EUI in the application:__
19.2	165
	166
50.2	167	[[image:1664501711466-918.png]]
19.2	168
	169
	170
50.2	171	[[image:1664501721248-725.png]]
19.2	172
	173
50.2	174	[[image:1664501734705-405.png]]
19.2	175
	176
	177
50.2	178	__Add APP KEY and DEV EUI:__
19.2	179
	180
50.2	181	[[image:1664501784668-703.png]]
19.2	182
	183
	184
	185
50.2	186	(% style="color:blue" %)Step 2:(%%) Power on TrackerD by using the on board switch.
19.2	187
50.2	188
	189	(% style="color:blue" %)Step 3:(%%) TrackerD will auto join to the LoRaWAN network. After join success, TrackerD will start to upload message to IoT server.
	190
	191
68.4	192
66.3	193	== 2.3 Positioning Mode(SMOD) ==
50.2	194
66.3	195
55.1	196	Users can set TrackerD to different Positioning Mode for different applications. Below mod are supported.
19.2	197
55.1	198	* (% style="color:#037691" %)GPS ONLY(Factory Settings): (%%)only get and uplink GPS location info.
	199	* (% style="color:#037691" %)BLE ONLY: (%%)Only obtain iBeacon info via BLE and uplink. Design for Indoor tracking.
	200	* (% style="color:#037691" %)GPS/BLE Hybrid: (%%)Combination for Indoor and Outdoor tracking.Devices will try to search BLE iBeacon first. If device can't find the iBeacon, it will use GPS for positioning.
19.2	201
55.1	202	Users can switch modes by [[changing SMOD>>\|\|anchor="H3.2.7SetPositioningMode"]].
19.2	203
50.2	204
19.2	205
66.3	206	== 2.4 Uplink Payload ==
19.2	207
	208
66.3	209	=== 2.4.1 Uplink FPORT~=5, Device Status ===
66.2	210
66.3	211
74.1	212	Uplink the device configures with FPORT=5. Once TrackerD Joined the network, it will uplink this message to the server. After the first uplink, TrackerD will uplink Device Status every 12 hours.
19.2	213
76.1	214	Use can also get the Device Status uplink through the downlink command: Downlink: 0x2301
19.2	215
76.1	216
66.2	217	(% border="1.5" style="background-color:#ffffcc; color:green; width:520px" %)
	218	\|=(% scope="row" style="width: 108px;" %)Size(bytes)\|=(% style="width: 82px;" %)1\|=(% style="width: 83px;" %)2\|=(% style="width: 94px;" %)1\|=(% style="width: 84px;" %)1\|=(% style="width: 44px;" %)2\|=(% style="width: 63px;" %)2\|=(% style="width: 60px;" %)1
	219	\|=(% style="width: 108px;" %)Value\|(% style="width:82px" %)Sensor Model\|(% style="width:83px" %)Firmware Version\|(% style="width:94px" %)Frequency Band\|(% style="width:84px" %)Sub-band\|(% style="width:44px" %)BAT\|(% style="width:63px" %)SMOD\|(% style="width:60px" %)Status
19.2	220
66.2	221	[[image:1665301570342-765.png]]
	222
	223
74.2	224	(% style="color:#037691" %)Example of Device Status:(%%) 13014001FF0FA24002
19.2	225
74.2	226	(% style="color:#037691" %)Sensor Model: (%%) For TrackerD,this value is 0x13
19.2	227
74.2	228	(% style="color:#037691" %)Firmware Version: (%%) 0x0140,Means:v1.4.0 version
50.2	229
74.2	230	(% style="color:#037691" %)Frequency Band:
55.1	231
	232	*0x01: EU868
	233
	234	*0x02: US915
	235
	236	*0x03: IN865
	237
	238	*0x04: AU915
	239
	240	*0x05: KZ865
	241
	242	*0x06: RU864
	243
	244	*0x07: AS923
	245
	246	*0x08: AS923-1
	247
	248	*0x09: AS923-2
	249
	250	*0x0a: AS923-3
	251
74.2	252	Sub- Band:value 0x00~~0x08(only forAU915,US915,Others are 0xFF)
55.1	253
74.2	254	(% style="color:#037691" %)BAT:(%%) shows the battery voltage for TrackerD.
55.1	255
	256
74.2	257	(% style="color:#037691" %)Ex1:(%%) 0x0FA2 = 4002mV
	258
55.1	259	Use can also get the Device Status uplink through the downlink command:
	260
	261
75.1	262	(% style="color:#037691" %)SMOD Field (total 1 byte)(%%)：0x40
74.2	263
75.1	264	(% border="1.5" style="background-color:#ffffcc; color:green; width:420px" %)
	265	\|(% style="width:75px" %)Size(bit)\|(% style="width:64px" %)2bits\|(% style="width:137px" %)2bit\|(% style="width:142px" %)4bit
	266	\|(% style="width:75px" %)Value\|(% style="width:64px" %)SMOD\|(% style="width:137px" %)GPS_Settings\|(% style="width:142px" %)BLE_Settings
74.2	267
75.1	268	(% style="color:blue" %) SMOD：
74.2	269
75.1	270	(% style="color:red" %) 1 : (%%) GPS ONLY
74.2	271
75.1	272	(% style="color:red" %) 2 : (%%) BLE ONLY
74.2	273
75.1	274	(% style="color:red" %) 3 : (%%) GPS/BLE Hybrid
74.2	275
	276
75.1	277	(% style="color:blue" %) GPS_MOD: Define how to send GPS payload
74.2	278
75.1	279	(% style="color:red" %) 0 : (%%) Enable uploading on-board Temperature and humidity values
74.2	280
75.1	281	(% style="color:red" %) 1 : (%%) Disable uploading on-board Temperature and humidity values
74.2	282
	283
75.1	284	(% style="color:blue" %) BLE_Settings:
74.2	285
75.1	286	(% style="color:red" %) 1: (%%) BLE Positioning with Strongest iBeacon
74.2	287
	288
75.1	289	(% style="color:#037691" %)Status Field (total 1 byte)(%%): 0x02
74.2	290
78.3	291	(% border="1.5" style="background-color:#ffffcc; color:green; width:417px" %)
	292	\|(% style="width:77px" %)Size(bit)\|(% style="width:70px" %)5 Bits\|(% style="width:92px" %)1 Bit\|(% style="width:48px" %)1 Bit\|(% style="width:126px" %)1 Bit
	293	\|(% 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	294
84.2	295
	296
66.3	297	=== 2.4.2 Uplink FPORT~=2, Realtime GNSS Positioning + Temperature & Humidity ===
55.1	298
	299
77.1	300	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	301
	302
51.24	303	(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:480px" %)
51.23	304	\|=(% scope="row" style="width: 50px;" %)(((
51.21	305	Size(bytes)
59.2	306	)))\|(% style="width:60px" %)4\|(% style="width:70px" %)4\|(% style="width:80px" %)2\|(% style="width:73px" %)1\|(% style="width:40px" %)(((
	307	2
51.24	308	)))\|(% style="width:87px" %)(((
59.2	309	2
19.2	310	)))
51.18	311	\|=(% style="width: 69px;" %)Value\|(% style="width:76px" %)[[Latitude>>\|\|anchor="HLocationinfo:"]]\|(% style="width:87px" %)[[Longitude>>\|\|anchor="HLocationinfo:"]]\|(% style="width:76px" %)(((
51.5	312	[[Alarm & BAT>>\|\|anchor="HAlarm26BAT:"]]
59.2	313	)))\|(% style="width:73px" %)[[FLAG>>\|\|anchor="HFLAG:"]]\|(% style="width:40px" %)[[Hum>>\|\|anchor="HHum:"]]\|(% style="width:87px" %)[[Tem>>\|\|anchor="HTem:"]]
19.2	314
66.2	315	[[image:1665301636888-168.png]]
19.2	316
50.2	317
51.24	318	==== (% style="color:blue" %)Alarm & BAT:(%%) ====
19.2	319
51.24	320	(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:250px" %)
	321	\|=(% scope="row" style="width: 50px;" %)Size(bit)\|(% style="width:50px" %)1 bit\|(% style="width:80px" %)1bit\|(% style="width:50px" %)14bits
51.22	322	\|=(% style="width: 72px;" %)Value\|(% style="width:67px" %)reserve\|(% style="width:118px" %)Alarm Indicate\|(% style="width:63px" %)[[BAT>>\|\|anchor="HBAT:"]]
19.2	323
51.24	324	==== (% style="color:blue" %)FLAG:(%%) ====
	325
	326	(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:250px" %)
59.3	327	\|=(% scope="row" style="width: 50px;" %)Size(bit)\|(% style="width:50px" %)2bits\|(% style="width:50px" %)1bit
	328	\|=(% style="width: 79px;" %)Value\|(% style="width:55px" %)[[MOD>>\|\|anchor="H3.2.7SetPositioningMode"]]\|(% style="width:47px" %)[[LON>>\|\|anchor="HLON:"]]
19.2	329
51.11	330	Example: Payload: 0x02863D68 FAC29BAF 4B45 60 0202 011A
19.2	331
	332
51.24	333	==== (% style="color:blue" %)Location info:(%%) ====
19.2	334
51.11	335	* Latitude: 02863D68 ⇒ //if (0x//02863D68//& 0x80000000 = 0 )~:// //value = 02863D68 /1000000 = 42.351976//
	336	* Longitude: FAC29BAF ⇒ //if (0x//FAC29BAF// & 0x80000000 = 1 )~:// //value = (0x//FAC29BAF// – 0x 100000000)/1000000 =//-87.9094//57//
19.2	337
51.9	338	(% style="color:red" %)Important note:
19.2	339
50.2	340	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	341
59.3	342	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	343
	344
50.2	345	[[image:1664502116362-706.png]]
19.2	346
	347
59.3	348	3. While GPS can't get location info after timeout(FTIME Parameter), the latitude and longitude will be filled with all 0x00:
50.2	349
	350	[[image:1664502166010-515.png]]
	351
	352
	353
51.24	354	==== (% style="color:blue" %)Alarm:(%%) ====
50.2	355
74.9	356	Example: 0x4B & 0x40 >> 6 = 0x01
19.2	357
	358
51.24	359	==== (% style="color:blue" %)BAT:(%%) ====
51.6	360
74.9	361	Example: 0x4B45 & 0x3FFF ⇒ 2885 (mV).
51.6	362
51.27	363	(((
59.3	364	The battery info shows the battery voltage, User can use the below mapping to indicate the battery in percentage: \
51.27	365	)))
51.6	366
50.4	367	* > 4.0v : 80% ~~ 100%
	368	* 3.85v ~~3.99v: 60% ~~ 80%
	369	* 3.70v ~~ 3.84v: 40% ~~ 60%
	370	* 3.40v ~~ 3.69v: 20% ~~ 40%
	371	* < 3.39v: 0~~20%
19.2	372
84.2	373
	374
74.3	375	==== (% style="color:blue" %)MOD:(%%) ====
	376
79.1	377	Example: (0x60>>6) & 0x3f =1
74.10	378
74.7	379	Set the format of GPS data uplink link：
74.3	380
74.7	381	(% style="color:#037691" %)0x00: (%%) Enable uploading on-board Temperature and humidity values
74.9	382	(% style="color:#037691" %)0x01: (%%) Disable uploading on-board Temperature and humidity values
74.3	383
	384
74.7	385	Set the format of BLE data uplink link：
74.3	386
74.7	387	(% style="color:#037691" %)0x01: (%%) BLE Positioning with Strongest iBeacon
	388
	389
74.10	390	==== (% style="color:blue" %)LON:(%%) ====
74.9	391
74.10	392	Example: (0x60>>5) & 0x01=1.
74.9	393
51.4	394	Enable/Disable LED activity for uplink
19.2	395
51.27	396	(((
74.7	397	(% style="color:#037691" %)0x00: (%%) Disable LED indicator.
51.27	398	)))
19.2	399
51.27	400	(((
74.7	401	(% style="color:#037691" %)0x01: (%%) Enable LED indicator (Default Value)
51.27	402	)))
19.2	403
	404
74.9	405
51.24	406	==== (% style="color:blue" %)Hum:(%%) ====
19.2	407
51.4	408	0202 = //if (0x0202 & 0x8000 = 0 ): value =// 0x0202 / 100 = +514 ⇒ 51.4 degree
19.2	409
	410
51.24	411	==== (% style="color:blue" %)Tem:(%%) ====
19.2	412
51.9	413	011A =if (0x011A & 0x8000 = 1 ): value =( 0x011A - 0x10000)/10(dec) ⇒ -//28.2 degree//
51.4	414
	415
66.2	416
66.3	417	=== 2.4.3 Uplink FPORT~=3, Realtime GNSS Positioning (Default Mode) ===
51.4	418
66.2	419
78.1	420	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	421
	422
59.2	423	(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:480px" %)
	424	\|=(% scope="row" style="width: 50px;" %)(((
	425	Size(bytes)
	426	)))\|(% style="width:60px" %)4\|(% style="width:70px" %)4\|(% style="width:80px" %)2\|(% style="width:73px" %)1
	427	\|=(% style="width: 69px;" %)Value\|(% style="width:76px" %)[[Latitude>>\|\|anchor="HLocationinfo:"]]\|(% style="width:87px" %)[[Longitude>>\|\|anchor="HLocationinfo:"]]\|(% style="width:76px" %)(((
	428	[[Alarm & BAT>>\|\|anchor="HAlarm26BAT:"]]
	429	)))\|(% style="width:73px" %)[[FLAG>>\|\|anchor="HFLAG:"]]
50.2	430
66.2	431	(% class="wikigeneratedid" %)
	432	[[image:1665301687277-443.png]]
	433
	434
	435
66.3	436	=== 2.4.4 Uplink FPORT~=4, History GNSS Positioning ===
59.2	437
66.2	438
78.2	439	Set [[PNACKMD=1>>\|\|anchor="H3.2.10A0A0AutoSendNone-ACKmessages"]], and TrackerD will wait for ACK for every uplink, when there is no LoRaWAN network, TrackerD will mark these records with non-ack messages and store the sensor data, and it will send all messages (10s interval) after the network recovery.
59.2	440
66.2	441
66.3	442	(% style="color:red" %)Note for this mode:
59.2	443
59.3	444	* a) TrackerD will do an ACK check for data records sending to make sure every data arrive server.
66.3	445	* b) TrackerD will send data in (% style="color:blue" %)CONFIRMED Mode(%%) when PNACKMD=1, but TrackerD won't re-transmit the packet if it doesn't get ACK, it will just mark it as a NONE-ACK message. In a future uplink, if TrackerD gets an ACK, TrackerD will consider there is a network connection and resend all NONE-ACK Messages.
78.1	446	* 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	447
59.3	448	The payload is 15 bytes, as below.
50.2	449
66.2	450	(% border="1.5" style="background-color:#ffffcc; color:green; width:520px" %)
	451	\|=(% scope="row" %)(((
	452	Size(bytes)
	453	)))\|4\|4\|2\|1\|1\|1\|1\|1
66.3	454	\|=Value\|Latitude\|Longitude\|Year\|Month\|Day\|Hous\|Min\|Sen
59.3	455
68.2	456	[[image:image-20221009160309-2.png]]
59.3	457
66.2	458
	459
66.3	460	=== 2.4.5 Uplink FPORT~=6, BLE Positioning with Strongest iBeacon ===
59.3	461
84.2	462
81.1	463	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	464
82.1	465	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	466
81.1	467
51.25	468	(% border="1.5" cellspacing="3" style="background-color:#ffffcc; color:green; width:450px" %)
51.26	469	\|=(% scope="row" style="width: 60px;" %)(((
51.24	470	Size(bytes)
51.26	471	)))\|(% 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	472	\|=(% style="width: 50px;" %)Value\|(% style="width:44px" %)[[UUID>>\|\|anchor="HLocationinfo:"]]\|(% style="width:61px" %)(((
51.8	473	iBeacon MAJOR
51.11	474	)))\|(% style="width:63px" %)(((
	475	iBeacon MINOR
50.2	476	)))\|(% style="width:71px" %)(((
51.8	477	iBeacon Measured Power
51.11	478	)))\|(% style="width:50px" %)(((
51.8	479	iBeacon RSSI
51.11	480	)))\|(% style="width:47px" %)(((
51.8	481	[[Alarm & BAT>>\|\|anchor="HAlarm26BAT:"]]
51.11	482	)))\|(% style="width:15px" %)[[FLAG>>\|\|anchor="HFLAG:"]]
19.2	483
50.2	484	[[image:1664502425687-834.png]]
19.2	485
	486
79.1	487	* (% style="color:#037691" %)BAT: (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV).
51.9	488	* (% style="color:#037691" %)MODE: (%%)Define the payload format.
	489	* (% style="color:#037691" %)UUID: (%%)The uuid from the strongest iBeacon.
	490	* (% style="color:#037691" %)MAJOR: (%%) The MAJOR from the strongest iBeacon.
	491	* (% style="color:#037691" %)MINOR: (%%)The MAJOR from the strongest iBeacon.
	492	* (% style="color:#037691" %)Measured Power: (%%) The Measured Power from the strongest iBeacon.
	493	* (% style="color:#037691" %)RSSI: (%%) The RSSI from the strongest iBeacon.
19.2	494
82.1	495
84.2	496
68.3	497	=== 2.4.6 Add Payload format in TTN V3 ===
19.3	498
50.2	499
19.2	500	In TTN V3, use can add a custom payload so it shows friendly.
	501
51.9	502	In the page (% style="color:#037691" %)Applications ~-~-> Payload Formats ~-~-> Custom ~-~-> decoder
19.2	503
	504
50.2	505	[[image:1664502649601-895.png]]
	506
51.9	507
78.7	508	Add the decoder from this link:
19.2	509
78.7	510	[[https:~~/~~/github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD>>https://github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD]]
19.2	511
	512	Save the change the uplink message will be parsed. As below:
	513
50.2	514	[[image:1664502676891-606.png]]
19.2	515
	516
	517
66.3	518	== 2.5 Integrate with Datacake ==
19.2	519
	520	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.
	521
50.2	522	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	523
50.2	524	[[image:1664502695771-538.png]]
19.2	525
50.2	526
	527
66.3	528	== 2.6 Integrate with Tago ==
19.2	529
	530
	531
81.1	532	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.
	533
19.2	534	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]]
	535
	536
81.1	537
50.2	538	[[image:1664502715371-321.png]]
19.2	539
	540
	541
68.4	542	== 2.7 Datalog Feature ==
56.1	543
68.4	544
78.1	545	total 273 entries,by default,
56.1	546
78.4	547	User can set [[PNACKMD=1>>\|\|anchor="H3.2.10A0A0AutoSendNone-ACKmessages"]], to enable Datalog feature.
68.4	548
71.1	549	Example use case.
68.4	550
72.1	551	[[image:image-20221009234703-2.png\|\|height="328" width="899"]]
71.1	552
	553
72.1	554	[[image:image-20221009234629-1.png\|\|height="390" width="577"]]
71.1	555
	556
	557
66.3	558	== 2.8 Alarm Mode ==
19.2	559
	560
51.27	561	(((
51.11	562	User can push the (% style="color:red" %)RED button(%%) by more than 5 seconds to enter Alarm Mode.
51.27	563	)))
19.2	564
	565
51.27	566	(((
81.1	567	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	568	)))
19.2	569
	570
51.27	571	(((
19.2	572	Two ways to exit alarm mode:
51.27	573	)))
19.2	574
81.1	575	* Server sends a downlink command to exit.
19.2	576	* User fast press the RED button 10 times.
	577
51.27	578	(((
51.11	579	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	580	)))
19.2	581
	582
50.2	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
55.1	589
68.4	590
66.3	591	== 2.10 LED Status ==
19.2	592
	593
51.26	594	(% border="1.5" style="background-color:#ffffcc; color:green; width:500px" %)
51.27	595	\|=(% style="width: 150px;" %)Event\|=(% style="width: 200px;" %)Action\|=(% style="width: 150px;" %)AT+LON to control on/off
51.11	596	\|(% 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
	597	\|(% style="width:157px" %)Join request\|(% style="width:271px" %)(% style="color:green" %)Green (%%)led fast blink once (200ms)\|(% style="width:202px" %)Yes
	598	\|(% style="width:157px" %)Join Success\|(% style="width:271px" %)(% style="color:green" %)Green(%%) led on 5 second\|(% style="width:202px" %)N/A
	599	\|(% style="width:157px" %)Fixing Location\|(% style="width:271px" %)(% style="color:blue" %)BLUE (%%)blinks 200ms per second\|(% style="width:202px" %)Yes
	600	\|(% style="width:157px" %)Fixed and uplink\|(% style="width:271px" %)(% style="color:green" %)GREEN (%%)blinks twice (200ms per blink)\|(% style="width:202px" %)Yes
	601	\|(% style="width:157px" %)Fail Fix and uplink\|(% style="width:271px" %)(% style="color:red" %)RED (%%)blinks twice (200ms per blink)\|(% style="width:202px" %)Yes
	602	\|(% style="width:157px" %)Enter Alarm mode\|(% style="width:271px" %)(% style="color:red" %)RED (%%)on for 3 seconds\|(% style="width:202px" %)Yes
	603	\|(% style="width:157px" %)Uplink under Alarm\|(% style="width:271px" %)(% style="color:red" %)RED (%%)on for 1 second\|(% style="width:202px" %)Yes
	604	\|(% style="width:157px" %)Exit Alarm\|(% style="width:271px" %)(% style="color:blue" %)BLUE (%%)led on 5 second\|(% style="width:202px" %)Yes
	605	\|(% style="width:157px" %)Get Downlink\|(% style="width:271px" %)(% style="color:green" %)GREEN(%%) led on 1 second\|(% style="width:202px" %)Yes
	606	\|(% style="width:157px" %)Movement Detect\|(% style="width:271px" %)(% style="color:red" %)RED (%%)led on 500ms\|(% style="width:202px" %)N/A
19.2	607
84.2	608
	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
50.2	615	[[image:1664502835802-546.png]]
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
50.2	622	[[image:1664502854406-763.png]]
19.2	623
	624
51.27	625	(% border="1.5" style="background-color:#ffffcc; color:green; width:520px" %)
	626	\|=(% style="width: 100px;" %)Function\|=(% style="width: 210px;" %)Action\|=(% style="width: 210px;" %)Description
51.11	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.6AlarmMode"]]
	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
84.2	631
	632
66.3	633	== 2.12 USB Port Function ==
19.2	634
50.2	635
19.2	636	The USB interface of TrackerD has below functions:
	637
	638	* Power on the device
	639	* Recharge the battery
51.11	640	* [[Configure Device>>\|\|anchor="H3.ConfigureTrackerDviaATcommandorLoRaWANdownlink"]]
	641	* [[Upgrade Firmware>>\|\|anchor="H5.UploadFirmware"]]
19.2	642
84.2	643
	644
19.3	645	= 3. Configure TrackerD via AT command or LoRaWAN downlink =
19.2	646
	647
	648	User can configure TrackerD via AT Command or LoRaWAN Downlink.
	649
51.13	650	LoRaWAN Downlink instruction for different platforms: [[IoT LoRaWAN Server>>doc:Main.WebHome]]
19.2	651
	652
50.2	653
19.3	654	== 3.1 Access AT Command ==
19.2	655
	656
50.2	657	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	658
	659
50.2	660	[[image:1664502999401-486.png]]
	661
	662
51.11	663	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	664
	665
50.2	666	[[image:1664503022490-662.png]]
19.2	667
	668
50.2	669	[[image:1664503035713-500.png]]
19.2	670
	671
50.2	672	[[image:1664503047675-651.png]]
	673
	674
	675
19.3	676	== 3.2 Command Set ==
19.2	677
	678
19.3	679	=== 3.2.1 Set Transmit Interval ===
19.2	680
50.2	681
19.2	682	Set device uplink interval.
	683
51.13	684	* (% style="color:blue" %)AT Command:
19.2	685
51.13	686	(% style="color:#037691" %)AT+TDC=xxx
19.2	687
50.2	688	Example: AT+TDC=300000. Means set interval to 5 minutes(300 seconds)
19.2	689
	690
51.13	691	* (% style="color:blue" %)Downlink Payload (prefix 0x01):
19.2	692
51.13	693	(% style="color:#037691" %)0x01 00 01 2C (%%) ~/~/ Same as AT+TDC=300000
19.2	694
	695
50.2	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
	714
57.1	715	=== 3.2.3 Set Transport Mode Packet transmission interval ===
50.2	716
	717
57.1	718	Set Transport Mode packet transmit interval
19.2	719
51.13	720	* (% style="color:blue" %)AT Command:
19.2	721
51.13	722	(% style="color:#037691" %)AT+MTDC=xx.
19.2	723
57.1	724	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	725
	726
51.13	727	* (% style="color:blue" %)Downlink Payload (prefix 0x03):
19.2	728
51.13	729	(% style="color:#037691" %)0x03 00 01 2C (%%) ~/~/ Same as AT+ MTDC=3000000
19.2	730
	731
	732
50.2	733	=== 3.2.4 Exit Alarm ===
19.2	734
50.2	735
19.2	736	Server send downlink command to exit Alarm mode
	737
51.13	738	* (% style="color:blue" %)AT Command: No AT Command
19.2	739
51.13	740	* (% style="color:blue" %)Downlink Payload (prefix 0x02):
19.2	741
51.13	742	(% style="color:#037691" %)0x02 01 (%%) ~/~/ Exit Alarm Mode
19.2	743
51.13	744
	745
50.2	746	=== 3.2.5 Disable/Enable LED flash ===
	747
	748
19.2	749	Disable/Enable LED for position, downlink and uplink
	750
51.13	751	* (% style="color:blue" %)AT Command:
19.2	752
51.13	753	(% style="color:#037691" %)AT+LON=xx. (Disable (0), Enable (1), default:1)
19.2	754
51.28	755	Example: AT+LON=0 ~-~-> Disable LED for position, downlink and uplink.
19.2	756
	757
51.13	758	* (% style="color:blue" %)Downlink Payload (prefix 0xAE):
19.2	759
51.13	760	(% style="color:#037691" %)0xAE 00 (%%) ~/~/ Same as AT+LON=0
19.2	761
	762
	763
59.1	764	=== 3.2.6 Disable/Enable Transport Mode ===
19.2	765
	766
59.1	767	Users can use this feature to enable/disable Transport Mode.
19.2	768
51.13	769	* (% style="color:blue" %)AT Command:
19.2	770
51.13	771	(% style="color:#037691" %)AT+INTWK=xx. (Disable (0), Enable (1), default:0)
19.2	772
59.1	773	Example: AT+ INTWK =1 ~-~-> Enable Transport Mode.
19.2	774
	775
51.13	776	* (% style="color:blue" %)Downlink Payload (prefix 0xAF):
19.2	777
51.13	778	(% style="color:#037691" %)0xAF 01 (%%) ~/~/ Same as AT+ INTWK =1
19.2	779
	780
	781
50.2	782	=== 3.2.7 Set Positioning Mode ===
19.2	783
50.2	784
79.1	785	SMOD define how TrackerD scan and uplink data:
19.2	786
	787
51.13	788	* (% style="color:blue" %)AT Command:
19.2	789
74.5	790	(% style="color:#037691" %)AT+SMOD=aa,bb,cc
19.2	791
60.2	792	(% style="color:#037691" %) aa:
19.2	793
74.5	794	* (% style="color:red" %)1: GPS ONLY(Factory Settings): (%%)only get and uplink GPS location info.
	795	* (% style="color:red" %)2: BLE ONLY: (%%)Only obtain iBeacon info via BLE and uplink. Design for Indoor tracking.
	796	* (% 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	797
	798	(% style="color:#037691" %)bb:
	799
74.5	800	* (% style="color:red" %)0 : (%%)GPS+ BAT+ State+Tem&Hum
	801	* (% style="color:red" %)1 :(%%) GPS +BAT State
60.2	802
74.5	803	(% style="color:#037691" %)cc:
60.2	804
74.5	805	* (% style="color:red" %)1 : (%%) (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State
60.2	806
74.5	807	(% style="color:blue" %)Example:
19.2	808
79.1	809	AT+ SMOD =1,0,0 ~-~-> GPS+ BAT+ State+Tem&Hum
74.5	810	AT+ SMOD =1,1,0 ~-~-> GPS +BAT State
	811	AT+ SMOD =2,0,1 ~-~-> (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State
19.2	812
	813
51.13	814	* (% style="color:blue" %)Downlink Payload (prefix 0xA5):
19.2	815
74.5	816	(% style="color:#037691" %)0xA5 01 00 00 (%%) ~/~/ Same as AT+ SMOD =1,0,0
19.2	817
	818
	819
50.2	820	=== 3.2.8 Set MAX GPS position time ===
	821
	822
19.2	823	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.
	824
	825
	826	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.
	827
	828
51.13	829	* (% style="color:blue" %)AT Command:
19.2	830
51.13	831	(% style="color:#037691" %)AT+FTIME=xx (%%) ~-~-> Set to use xx as max fix time.
19.2	832
74.5	833	Example: AT+FTIME=150
19.2	834
	835
51.13	836	* (% style="color:blue" %)Downlink Payload (prefix 0xAA):
19.2	837
51.13	838	(% style="color:#037691" %)0xAA 00 96 (%%) ~/~/ Set AT+FTIME=150
19.2	839
	840
	841
68.4	842	=== 3.2.9 Set PDOP value for GPS fix accuracy ===
19.2	843
	844
50.2	845	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	846
50.2	847
19.2	848	A GPS packet with lower PDOP has higher accuracy. PDOP default value is 2.0
	849
	850
51.13	851	* (% style="color:blue" %)AT Command:
19.2	852
51.13	853	(% style="color:#037691" %)AT+PDOP=2.5 (%%) ~-~-> Set PDOP to 2.5
19.2	854
	855
51.13	856	* (% style="color:blue" %)Downlink Payload (prefix 0xAD):
19.2	857
51.13	858	(% style="color:#037691" %)0xAD 00 0A (%%) ~/~/ Set AT+PDOP=1 (0x0A / 10 =1)
19.2	859
51.13	860	(% style="color:#037691" %)0xAD 00 19 (%%) ~/~/ Set AT+PDOP=2.5 (0x19 / 10 =2.5)
19.2	861
51.13	862	(% style="color:#037691" %)0xAD 00 46 (%%) ~/~/ Set AT+PDOP=7 (0x46 / 10 =7)
19.2	863
50.2	864
51.12	865
19.2	866	Disable/Enable the confirmation mode
	867
51.13	868	* (% style="color:blue" %)AT Command:
19.2	869
74.6	870	(% style="color:#037691" %)AT+CFM=xx
19.2	871
	872
50.2	873	~ Example:
19.2	874
51.2	875	AT+ CFM=0 ~-~-> Disable confirmation
19.2	876
50.2	877	AT+ CFM=1 ~-~-> Enable confirmation
19.2	878
50.2	879
51.13	880	* (% style="color:blue" %)Downlink Payload (prefix 0x05):
19.2	881
51.13	882	(% style="color:#037691" %)0x05 01 (%%) ~/~/ Same as AT+ SMOD =1
19.2	883
	884
	885
74.6	886	=== 3.2.10 Auto Send None-ACK messages ===
	887
	888
	889	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.
	890
	891
	892	* (% style="color:blue" %)AT Command: AT+PNACKMD
	893
	894	The default factory setting is 0.
	895
	896
	897	Command Example Function Response:
	898
	899	(% style="color:#037691" %)AT+PNACKMD=1 (%%) ~/~/ Poll None-ACK message OK
	900
	901
	902	* (% style="color:blue" %)Downlink Command: 0x34
	903
	904	Example: 0x3401 ~/~/ Same as AT+PNACKMD=1
	905
	906
84.2	907
80.1	908	=== 3.2.11 Set BLEMASK to filter BLE iBeacon ===
	909
84.2	910
80.1	911	BLEMASK is to filter the unwanted BLE iBeacons during scan. For example, if BLEMASK is 123456. LBT1 will only uplink UUID info which includes 123456. It will ignore all other iBeacons which doesn’t contact 123456 in the UUID.
	912
	913	Note: BLEMASK range is 6 ~~ 10 bytes. If AT+BLEMASK < 6 bytes, BLEMASK will be disabled.
	914
	915	(% style="color:blue" %)AT Command:(%%)
	916	AT+BLEMASK=123456 ~/~/ Set BLEMASK = 123456
	917	AT+BLEMASK=0 ~/~/ disable BLEMASK
	918
	919
	920	(% style="color:blue" %)Downlink Payload: (Prefix : 0xA5)(%%)
	921	Example:
	922	0xA5010203040506 ~/~/ Set BLEMASK to 123456
	923
	924
	925
19.4	926	= 4. Setting for Different Scenarios =
19.2	927
	928
	929
19.4	930	= 5. Upload Firmware =
19.2	931
19.4	932
	933	== 5.1 Firmware Change Log ==
	934
50.2	935
19.2	936	[[See this link>>url:https://github.com/dragino/TrackerD]]
	937
	938
50.2	939
19.4	940	== 5.2 How to upgrade firmware ==
19.2	941
	942
50.2	943	User can use the TrackerD's USB port to upgrade firmware into it. The hardware connection for upgrade firmware is as below:
19.2	944
	945
50.2	946	(% style="color:blue" %)Step1: (%%)Connect TrackerD and PC via USB cable shipped with TrackerD.
19.2	947
50.2	948
	949	(% style="color:blue" %)Step2: (%%) Install CH9102 driver in the PC.
	950
19.2	951	After installation of the driver and plug in TrackerD, user should be able to see com port in PC's device manager.
	952
	953
51.28	954	(% 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	955
	956
50.2	957	(% style="color:blue" %)Step4: (%%) Run Flash Download Tool and configure chip type to ESP32
19.2	958
	959
50.2	960	[[image:1664503563660-578.png]]
19.2	961
	962
50.2	963	[[image:1664503574618-659.png]]
19.2	964
50.2	965
84.2	966	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.
	967
	968	[[image:image-20221024105643-1.png]]
	969
	970	Figure1
	971
	972
	973	[[image:image-20221024105643-2.png]]
	974
	975	Figure2
	976
	977
50.2	978	(% style="color:blue" %)Step5: (%%) Select the firmware file (.bin format), com port and proper SPI configure. Clink Start. Bin file location:
	979
73.1	980	[[https:~~/~~/github.com/dragino/TrackerD/releases>>https://github.com/dragino/TrackerD/releases]]
19.2	981
	982
	983	Users need to use below files:
	984
	985	boot_app0.bin @0e000
	986
	987	ESP_LORA-eeprom-class.bin @ 0x10000
	988
	989
50.2	990	[[image:1664503593459-435.png]]
19.2	991
	992
	993
50.2	994	After upgrade finish, it will show finish as below:
19.2	995
50.2	996	[[image:1664503611848-385.png]]
19.2	997
	998
50.2	999
19.4	1000	= 6. Developer Guide =
19.2	1001
	1002
19.4	1003	== 6.1 Compile Source Code ==
	1004
	1005
	1006	=== 6.1.1 Set up ARDUINO compile environment ===
	1007
	1008
51.28	1009	* 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	1010
51.15	1011	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	1012
	1013
50.2	1014	[[image:1664503635019-941.png]]
19.2	1015
50.2	1016
68.4	1017
51.28	1018	* (% style="color:#037691" %)Go to tools ~-~-> Boards ~-~-> Boards Manager,(%%) find the esp32 information and install it.
19.2	1019
50.2	1020	[[image:1664503715811-892.png]]
19.2	1021
	1022
	1023
51.28	1024	* Download the latest TrackerD from the dragino github: [[https:~~/~~/github.com/dragino/TrackerD>>url:https://github.com/dragino/TrackerD]]
19.2	1025
50.2	1026	Put the Library in the TrackerD directory into the libraries file in the Arduino directory:
19.2	1027
	1028
50.2	1029	[[image:1664503752288-974.png]]
19.2	1030
50.2	1031
	1032
19.4	1033	== 6.2 Source Code ==
	1034
	1035
51.16	1036	* (% style="color:blue" %)Open the example in the TrackerD file, please select the correct port in the IDE, as shown below:
19.2	1037
50.2	1038	[[image:1664503794261-827.png]]
19.2	1039
	1040
	1041
51.16	1042	* (% style="color:blue" %)Click to upload
19.2	1043
50.2	1044	[[image:1664503808294-336.png]]
19.2	1045
	1046
	1047
51.16	1048	* (% style="color:blue" %)Check the result, if the upload is successful, as shown below, open the serial port to view the data
19.2	1049
50.2	1050	[[image:1664503824081-592.png]] [[image:1664503831430-500.png]]
19.2	1051
	1052
	1053
18.2	1054	= 7. FAQ =
15.2	1055
	1056
18.2	1057	== 7.1 How to change the LoRa Frequency Bands/Region? ==
14.1	1058
	1059
51.14	1060	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	1061
12.1	1062
2.1	1063
18.2	1064	== 7.2 What is the pin mapping for the USB program cable? ==
2.1	1065
7.1	1066
18.2	1067	[[image:1664499635206-262.png]]
7.1	1068
	1069
	1070
51.28	1071	(% border="1.5" cellspacing="3" style="background-color:#ffffcc; color:green; width:314px" %)
51.27	1072	\|=(% style="width: 118px;" %)Pin\|=(% style="width: 67px;" %)Color\|=(% style="width: 123px;" %)USB Pin
18.2	1073	\|(% style="width:118px" %)A4,B4,A9,B9\|(% style="width:67px" %)Red\|(% style="width:123px" %)VCC
	1074	\|(% style="width:118px" %)A7,B7\|(% style="width:67px" %)White\|(% style="width:123px" %)D- (N/A)
	1075	\|(% style="width:118px" %)A6,B6\|(% style="width:67px" %)Green\|(% style="width:123px" %)D+(N/A)
	1076	\|(% style="width:118px" %)A1,B1,A12,B12\|(% style="width:67px" %)Black\|(% style="width:123px" %)GND
	1077	\|(% style="width:118px" %)A5\|(% style="width:67px" %)Purple\|(% style="width:123px" %)MTDC/GOIO13
	1078	\|(% style="width:118px" %)B5\|(% style="width:67px" %)Blue\|(% style="width:123px" %)MTDC/GPIO12
	1079	\|(% style="width:118px" %)A8\|(% style="width:67px" %)Yellow\|(% style="width:123px" %)MTMS/GPIO14
	1080	\|(% style="width:118px" %)B8\|(% style="width:67px" %)Grey\|(% style="width:123px" %)MTDO/GPIO15
7.1	1081
18.2	1082	= 8. Order Info =
7.1	1083
	1084
15.6	1085	Part Number: (% style="color:blue" %)TrackerD-XXX
8.1	1086
15.6	1087	(% style="color:blue" %)XXX(%%): The default frequency band
8.1	1088
15.6	1089	* (% style="color:red" %)EU433(%%): Default frequency band EU433
	1090	* (% style="color:red" %)EU868(%%): Default frequency band EU868
	1091	* (% style="color:red" %)IN865(%%): Default frequency band IN865
	1092	* (% style="color:red" %)KR920(%%): Default frequency band KR920
	1093	* (% style="color:red" %)AS923(%%): Default frequency band AS923
	1094	* (% style="color:red" %)AU915(%%): Default frequency band AU915
	1095	* (% style="color:red" %)US915(%%): Default frequency band US915
15.2	1096
84.2	1097
	1098
18.2	1099	= 9. Packing Info =
	1100
	1101
51.30	1102	(% style="color:#037691" %)Package Includes:
8.1	1103
50.3	1104	* TrackerD LoRaWAN GPS/BLE Tracker x 1
	1105	* USB recharge & program cable x 1
12.1	1106
51.30	1107	(% style="color:#037691" %)Dimensions and Weight:
12.1	1108
50.3	1109	* Device Size: 85 x 48 x 15 cm
	1110	* Weight: 50g
15.6	1111
84.2	1112
	1113
18.2	1114	= 10. Support =
	1115
50.3	1116
18.2	1117	* Support is provided Monday to Friday, from 09:00 to 18:00 GMT+8. Due to different timezones we cannot offer live support. However, your questions will be answered as soon as possible in the before-mentioned schedule.
51.28	1118	* 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	1119
84.2	1120
	1121
18.2	1122	= 11. Reference =
	1123
	1124
12.1	1125	* [[Firmware in Bin format>>https://www.dropbox.com/sh/733s8xlwahhqg1d/AABxDz80lBVX_to8zNuUQWFja?dl=0]]
	1126	* [[Source Code>>https://github.com/dragino/TrackerD]]
	1127	* [[Hardware Source>>https://www.dropbox.com/sh/orwoy6cecb89m4e/AAD37sRuUrvKsHgAJxuVTkB5a?dl=0]]
51.28	1128
68.2	1129

Wiki source code of TrackerD -LoRaWAN Tracker User Manual

Applications