Wiki source code of TrackerD -LoRaWAN Tracker User Manual

Version 85.1 by Kilight Cao on 2022/11/01 15:43

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.19	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.19	120
	121
19.2	122	== 1.4 Applications ==
	123
	124
12.1	125	* Logistics and Supply Chain Management
	126	* Human tracking
	127
84.19	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
84.8	217	(% border="1.5" style="background-color:#ffffcc; color:green; width:440px" %)
84.9	218	\|=(% style="width: 60px;" %)Size(bytes)\|=(% style="width: 70px;" %)1\|=(% style="width: 70px;" %)2\|=(% style="width: 70px;" %)1\|=(% style="width: 50px;" %)1\|=(% style="width: 30px;" %)2\|=(% style="width: 40px;" %)2\|=(% style="width: 40px;" %)1
66.2	219	\|=(% style="width: 108px;" %)Value\|(% style="width:82px" %)Sensor Model\|(% style="width:83px" %)Firmware Version\|(% style="width:94px" %)Frequency Band\|(% style="width:84px" %)Sub-band\|(% style="width:44px" %)BAT\|(% style="width:63px" %)SMOD\|(% style="width:60px" %)Status
19.2	220
66.2	221	[[image:1665301570342-765.png]]
	222
	223
74.2	224	(% style="color:#037691" %)Example of Device Status:(%%) 13014001FF0FA24002
19.2	225
74.2	226	(% style="color:#037691" %)Sensor Model: (%%) For TrackerD,this value is 0x13
19.2	227
74.2	228	(% style="color:#037691" %)Firmware Version: (%%) 0x0140,Means:v1.4.0 version
50.2	229
74.2	230	(% style="color:#037691" %)Frequency Band:
55.1	231
	232	*0x01: EU868
	233
	234	*0x02: US915
	235
	236	*0x03: IN865
	237
	238	*0x04: AU915
	239
	240	*0x05: KZ865
	241
	242	*0x06: RU864
	243
	244	*0x07: AS923
	245
	246	*0x08: AS923-1
	247
	248	*0x09: AS923-2
	249
	250	*0x0a: AS923-3
	251
74.2	252	Sub- Band:value 0x00~~0x08(only forAU915,US915,Others are 0xFF)
55.1	253
74.2	254	(% style="color:#037691" %)BAT:(%%) shows the battery voltage for TrackerD.
55.1	255
	256
74.2	257	(% style="color:#037691" %)Ex1:(%%) 0x0FA2 = 4002mV
	258
55.1	259	Use can also get the Device Status uplink through the downlink command:
	260
	261
75.1	262	(% style="color:#037691" %)SMOD Field (total 1 byte)(%%)：0x40
74.2	263
84.11	264	(% border="1.5" style="background-color:#ffffcc; color:green; width:270px" %)
84.10	265	\|=(% scope="row" style="width: 60px;" %)Size(bit)\|(% style="width:50px" %)2bits\|(% style="width:80px" %)2bit\|(% style="width:80px" %)4bit
84.9	266	\|=(% style="width: 75px;" %)Value\|(% style="width:64px" %)SMOD\|(% style="width:104px" %)GPS_Settings\|(% style="width:103px" %)BLE_Settings
74.2	267
75.1	268	(% style="color:blue" %) SMOD：
74.2	269
75.1	270	(% style="color:red" %) 1 : (%%) GPS ONLY
74.2	271
75.1	272	(% style="color:red" %) 2 : (%%) BLE ONLY
74.2	273
75.1	274	(% style="color:red" %) 3 : (%%) GPS/BLE Hybrid
74.2	275
	276
75.1	277	(% style="color:blue" %) GPS_MOD: Define how to send GPS payload
74.2	278
75.1	279	(% style="color:red" %) 0 : (%%) Enable uploading on-board Temperature and humidity values
74.2	280
75.1	281	(% style="color:red" %) 1 : (%%) Disable uploading on-board Temperature and humidity values
74.2	282
	283
75.1	284	(% style="color:blue" %) BLE_Settings:
74.2	285
75.1	286	(% style="color:red" %) 1: (%%) BLE Positioning with Strongest iBeacon
74.2	287
	288
75.1	289	(% style="color:#037691" %)Status Field (total 1 byte)(%%): 0x02
74.2	290
84.11	291	(% border="1.5" style="background-color:#ffffcc; color:green; width:260px" %)
	292	\|=(% 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	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.19	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
84.13	303	(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:320px" %)
	304	\|=(% scope="row" style="width: 60px;" %)(((
84.19	305	Size(bytes)
	306	)))\|(% style="width:50px" %)4\|(% style="width:50px" %)4\|(% style="width:70px" %)2\|(% style="width:30px" %)1\|(% style="width:30px" %)(((
	307	2
	308	)))\|(% style="width:30px" %)(((
	309	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
84.19	324
	325
51.24	326	==== (% style="color:blue" %)FLAG:(%%) ====
	327
84.12	328	(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:120px" %)
	329	\|=(% scope="row" style="width: 50px;" %)Size(bit)\|(% style="width:30px" %)2bits\|(% style="width:30px" %)1bit
59.3	330	\|=(% style="width: 79px;" %)Value\|(% style="width:55px" %)[[MOD>>\|\|anchor="H3.2.7SetPositioningMode"]]\|(% style="width:47px" %)[[LON>>\|\|anchor="HLON:"]]
19.2	331
51.11	332	Example: Payload: 0x02863D68 FAC29BAF 4B45 60 0202 011A
19.2	333
	334
51.24	335	==== (% style="color:blue" %)Location info:(%%) ====
19.2	336
51.11	337	* Latitude: 02863D68 ⇒ //if (0x//02863D68//& 0x80000000 = 0 )~:// //value = 02863D68 /1000000 = 42.351976//
	338	* Longitude: FAC29BAF ⇒ //if (0x//FAC29BAF// & 0x80000000 = 1 )~:// //value = (0x//FAC29BAF// – 0x 100000000)/1000000 =//-87.9094//57//
19.2	339
84.19	340
	341
51.9	342	(% style="color:red" %)Important note:
19.2	343
50.2	344	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	345
59.3	346	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	347
	348
50.2	349	[[image:1664502116362-706.png]]
19.2	350
	351
59.3	352	3. While GPS can't get location info after timeout(FTIME Parameter), the latitude and longitude will be filled with all 0x00:
50.2	353
	354	[[image:1664502166010-515.png]]
	355
	356
	357
51.24	358	==== (% style="color:blue" %)Alarm:(%%) ====
50.2	359
74.9	360	Example: 0x4B & 0x40 >> 6 = 0x01
19.2	361
	362
51.24	363	==== (% style="color:blue" %)BAT:(%%) ====
51.6	364
74.9	365	Example: 0x4B45 & 0x3FFF ⇒ 2885 (mV).
51.6	366
51.27	367	(((
59.3	368	The battery info shows the battery voltage, User can use the below mapping to indicate the battery in percentage: \
51.27	369	)))
51.6	370
50.4	371	* > 4.0v : 80% ~~ 100%
	372	* 3.85v ~~3.99v: 60% ~~ 80%
	373	* 3.70v ~~ 3.84v: 40% ~~ 60%
	374	* 3.40v ~~ 3.69v: 20% ~~ 40%
	375	* < 3.39v: 0~~20%
19.2	376
84.19	377
	378
74.3	379	==== (% style="color:blue" %)MOD:(%%) ====
	380
79.1	381	Example: (0x60>>6) & 0x3f =1
74.10	382
74.7	383	Set the format of GPS data uplink link：
74.3	384
74.7	385	(% style="color:#037691" %)0x00: (%%) Enable uploading on-board Temperature and humidity values
74.9	386	(% style="color:#037691" %)0x01: (%%) Disable uploading on-board Temperature and humidity values
74.3	387
	388
74.7	389	Set the format of BLE data uplink link：
74.3	390
74.7	391	(% style="color:#037691" %)0x01: (%%) BLE Positioning with Strongest iBeacon
	392
	393
74.10	394	==== (% style="color:blue" %)LON:(%%) ====
74.9	395
74.10	396	Example: (0x60>>5) & 0x01=1.
74.9	397
51.4	398	Enable/Disable LED activity for uplink
19.2	399
51.27	400	(((
74.7	401	(% style="color:#037691" %)0x00: (%%) Disable LED indicator.
51.27	402	)))
19.2	403
51.27	404	(((
74.7	405	(% style="color:#037691" %)0x01: (%%) Enable LED indicator (Default Value)
51.27	406	)))
19.2	407
	408
51.24	409	==== (% style="color:blue" %)Hum:(%%) ====
19.2	410
51.4	411	0202 = //if (0x0202 & 0x8000 = 0 ): value =// 0x0202 / 100 = +514 ⇒ 51.4 degree
19.2	412
	413
51.24	414	==== (% style="color:blue" %)Tem:(%%) ====
19.2	415
51.9	416	011A =if (0x011A & 0x8000 = 1 ): value =( 0x011A - 0x10000)/10(dec) ⇒ -//28.2 degree//
51.4	417
	418
66.2	419
66.3	420	=== 2.4.3 Uplink FPORT~=3, Realtime GNSS Positioning (Default Mode) ===
51.4	421
66.2	422
78.1	423	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	424
	425
84.14	426	(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:300px" %)
84.19	427	\|=(% scope="row" style="width: 60px;" %)(((
	428	Size(bytes)
	429	)))\|(% style="width:60px" %)4\|(% style="width:60px" %)4\|(% style="width:60px" %)2\|(% style="width:50px" %)1
59.2	430	\|=(% style="width: 69px;" %)Value\|(% style="width:76px" %)[[Latitude>>\|\|anchor="HLocationinfo:"]]\|(% style="width:87px" %)[[Longitude>>\|\|anchor="HLocationinfo:"]]\|(% style="width:76px" %)(((
	431	[[Alarm & BAT>>\|\|anchor="HAlarm26BAT:"]]
	432	)))\|(% style="width:73px" %)[[FLAG>>\|\|anchor="HFLAG:"]]
50.2	433
66.2	434	(% class="wikigeneratedid" %)
	435	[[image:1665301687277-443.png]]
	436
	437
	438
66.3	439	=== 2.4.4 Uplink FPORT~=4, History GNSS Positioning ===
59.2	440
66.2	441
78.2	442	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	443
66.2	444
66.3	445	(% style="color:red" %)Note for this mode:
59.2	446
59.3	447	* a) TrackerD will do an ACK check for data records sending to make sure every data arrive server.
66.3	448	* 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	449	* 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	450
59.3	451	The payload is 15 bytes, as below.
50.2	452
84.15	453	(% border="1.5" style="background-color:#ffffcc; color:green; width:500px" %)
66.2	454	\|=(% scope="row" %)(((
	455	Size(bytes)
	456	)))\|4\|4\|2\|1\|1\|1\|1\|1
66.3	457	\|=Value\|Latitude\|Longitude\|Year\|Month\|Day\|Hous\|Min\|Sen
59.3	458
68.2	459	[[image:image-20221009160309-2.png]]
59.3	460
66.2	461
	462
66.3	463	=== 2.4.5 Uplink FPORT~=6, BLE Positioning with Strongest iBeacon ===
59.3	464
84.2	465
81.1	466	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	467
82.1	468	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	469
81.1	470
51.25	471	(% border="1.5" cellspacing="3" style="background-color:#ffffcc; color:green; width:450px" %)
51.26	472	\|=(% scope="row" style="width: 60px;" %)(((
51.24	473	Size(bytes)
51.26	474	)))\|(% 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	475	\|=(% style="width: 50px;" %)Value\|(% style="width:44px" %)[[UUID>>\|\|anchor="HLocationinfo:"]]\|(% style="width:61px" %)(((
51.8	476	iBeacon MAJOR
51.11	477	)))\|(% style="width:63px" %)(((
	478	iBeacon MINOR
50.2	479	)))\|(% style="width:71px" %)(((
51.8	480	iBeacon Measured Power
51.11	481	)))\|(% style="width:50px" %)(((
51.8	482	iBeacon RSSI
51.11	483	)))\|(% style="width:47px" %)(((
51.8	484	[[Alarm & BAT>>\|\|anchor="HAlarm26BAT:"]]
51.11	485	)))\|(% style="width:15px" %)[[FLAG>>\|\|anchor="HFLAG:"]]
19.2	486
50.2	487	[[image:1664502425687-834.png]]
19.2	488
	489
79.1	490	* (% style="color:#037691" %)BAT: (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV).
51.9	491	* (% style="color:#037691" %)MODE: (%%)Define the payload format.
	492	* (% style="color:#037691" %)UUID: (%%)The uuid from the strongest iBeacon.
	493	* (% style="color:#037691" %)MAJOR: (%%) The MAJOR from the strongest iBeacon.
	494	* (% style="color:#037691" %)MINOR: (%%)The MAJOR from the strongest iBeacon.
	495	* (% style="color:#037691" %)Measured Power: (%%) The Measured Power from the strongest iBeacon.
	496	* (% style="color:#037691" %)RSSI: (%%) The RSSI from the strongest iBeacon.
19.2	497
84.19	498
	499
68.3	500	=== 2.4.6 Add Payload format in TTN V3 ===
19.3	501
50.2	502
19.2	503	In TTN V3, use can add a custom payload so it shows friendly.
	504
51.9	505	In the page (% style="color:#037691" %)Applications ~-~-> Payload Formats ~-~-> Custom ~-~-> decoder
19.2	506
	507
50.2	508	[[image:1664502649601-895.png]]
	509
51.9	510
78.7	511	Add the decoder from this link:
19.2	512
78.7	513	[[https:~~/~~/github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD>>https://github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD]]
19.2	514
	515	Save the change the uplink message will be parsed. As below:
	516
50.2	517	[[image:1664502676891-606.png]]
19.2	518
	519
	520
66.3	521	== 2.5 Integrate with Datacake ==
19.2	522
84.5	523
19.2	524	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.
	525
50.2	526	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	527
50.2	528	[[image:1664502695771-538.png]]
19.2	529
50.2	530
	531
66.3	532	== 2.6 Integrate with Tago ==
19.2	533
	534
81.1	535	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.
	536
19.2	537	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]]
	538
	539
81.1	540
50.2	541	[[image:1664502715371-321.png]]
19.2	542
	543
	544
68.4	545	== 2.7 Datalog Feature ==
56.1	546
68.4	547
78.1	548	total 273 entries,by default,
56.1	549
78.4	550	User can set [[PNACKMD=1>>\|\|anchor="H3.2.10A0A0AutoSendNone-ACKmessages"]], to enable Datalog feature.
68.4	551
71.1	552	Example use case.
68.4	553
72.1	554	[[image:image-20221009234703-2.png\|\|height="328" width="899"]]
71.1	555
	556
72.1	557	[[image:image-20221009234629-1.png\|\|height="390" width="577"]]
71.1	558
	559
	560
66.3	561	== 2.8 Alarm Mode ==
19.2	562
	563
51.27	564	(((
51.11	565	User can push the (% style="color:red" %)RED button(%%) by more than 5 seconds to enter Alarm Mode.
51.27	566	)))
19.2	567
	568
51.27	569	(((
81.1	570	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	571	)))
19.2	572
	573
51.27	574	(((
19.2	575	Two ways to exit alarm mode:
51.27	576	)))
19.2	577
81.1	578	* Server sends a downlink command to exit.
19.2	579	* User fast press the RED button 10 times.
	580
51.27	581	(((
51.11	582	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	583	)))
19.2	584
	585
50.2	586
66.3	587	== 2.9 Transport Mode ==
19.2	588
	589
57.1	590	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	591
55.1	592
68.4	593
66.3	594	== 2.10 LED Status ==
19.2	595
	596
51.26	597	(% border="1.5" style="background-color:#ffffcc; color:green; width:500px" %)
51.27	598	\|=(% style="width: 150px;" %)Event\|=(% style="width: 200px;" %)Action\|=(% style="width: 150px;" %)AT+LON to control on/off
51.11	599	\|(% 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
	600	\|(% style="width:157px" %)Join request\|(% style="width:271px" %)(% style="color:green" %)Green (%%)led fast blink once (200ms)\|(% style="width:202px" %)Yes
	601	\|(% style="width:157px" %)Join Success\|(% style="width:271px" %)(% style="color:green" %)Green(%%) led on 5 second\|(% style="width:202px" %)N/A
	602	\|(% style="width:157px" %)Fixing Location\|(% style="width:271px" %)(% style="color:blue" %)BLUE (%%)blinks 200ms per second\|(% style="width:202px" %)Yes
	603	\|(% style="width:157px" %)Fixed and uplink\|(% style="width:271px" %)(% style="color:green" %)GREEN (%%)blinks twice (200ms per blink)\|(% style="width:202px" %)Yes
	604	\|(% style="width:157px" %)Fail Fix and uplink\|(% style="width:271px" %)(% style="color:red" %)RED (%%)blinks twice (200ms per blink)\|(% style="width:202px" %)Yes
	605	\|(% style="width:157px" %)Enter Alarm mode\|(% style="width:271px" %)(% style="color:red" %)RED (%%)on for 3 seconds\|(% style="width:202px" %)Yes
	606	\|(% style="width:157px" %)Uplink under Alarm\|(% style="width:271px" %)(% style="color:red" %)RED (%%)on for 1 second\|(% style="width:202px" %)Yes
	607	\|(% style="width:157px" %)Exit Alarm\|(% style="width:271px" %)(% style="color:blue" %)BLUE (%%)led on 5 second\|(% style="width:202px" %)Yes
	608	\|(% style="width:157px" %)Get Downlink\|(% style="width:271px" %)(% style="color:green" %)GREEN(%%) led on 1 second\|(% style="width:202px" %)Yes
	609	\|(% style="width:157px" %)Movement Detect\|(% style="width:271px" %)(% style="color:red" %)RED (%%)led on 500ms\|(% style="width:202px" %)N/A
19.2	610
84.19	611
	612
66.3	613	== 2.11 Button Function ==
19.2	614
50.2	615
51.27	616	(% style="color:blue" %)RESET button:
19.2	617
50.2	618	[[image:1664502835802-546.png]]
19.2	619
	620	Push this button will reboot the device. Device will exit alarm mode and re-join to LoRaWAN server.
	621
	622
51.11	623	(% style="color:red" %)RED button:
19.2	624
50.2	625	[[image:1664502854406-763.png]]
19.2	626
	627
84.18	628	(% border="1" style="background-color:#ffffcc; color:green; width:510px" %)
	629	\|=(% style="width: 100px;" %)Function\|=(% style="width: 205px;" %)Action\|=(% style="width: 205px;" %)Description
51.11	630	\|(% 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"]]
	631	\|(% 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	632	\|(% 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	633
84.19	634
	635
66.3	636	== 2.12 USB Port Function ==
19.2	637
50.2	638
19.2	639	The USB interface of TrackerD has below functions:
	640
	641	* Power on the device
	642	* Recharge the battery
51.11	643	* [[Configure Device>>\|\|anchor="H3.ConfigureTrackerDviaATcommandorLoRaWANdownlink"]]
	644	* [[Upgrade Firmware>>\|\|anchor="H5.UploadFirmware"]]
19.2	645
84.19	646
	647
19.3	648	= 3. Configure TrackerD via AT command or LoRaWAN downlink =
19.2	649
	650
	651	User can configure TrackerD via AT Command or LoRaWAN Downlink.
	652
51.13	653	LoRaWAN Downlink instruction for different platforms: [[IoT LoRaWAN Server>>doc:Main.WebHome]]
19.2	654
	655
50.2	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
50.2	663	[[image:1664502999401-486.png]]
	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
50.2	669	[[image:1664503022490-662.png]]
19.2	670
	671
50.2	672	[[image:1664503035713-500.png]]
19.2	673
	674
50.2	675	[[image:1664503047675-651.png]]
	676
	677
	678
19.3	679	== 3.2 Command Set ==
19.2	680
	681
19.3	682	=== 3.2.1 Set Transmit Interval ===
19.2	683
50.2	684
19.2	685	Set device uplink interval.
	686
51.13	687	* (% style="color:blue" %)AT Command:
19.2	688
51.13	689	(% style="color:#037691" %)AT+TDC=xxx
19.2	690
50.2	691	Example: AT+TDC=300000. Means set interval to 5 minutes(300 seconds)
19.2	692
	693
51.13	694	* (% style="color:blue" %)Downlink Payload (prefix 0x01):
19.2	695
51.13	696	(% style="color:#037691" %)0x01 00 01 2C (%%) ~/~/ Same as AT+TDC=300000
19.2	697
	698
50.2	699
19.3	700	=== 3.2.2 Set Alarm Packet transmission interval ===
19.2	701
50.2	702
19.2	703	Set alarm packet transmit interval
	704
51.13	705	* (% style="color:blue" %)AT Command:
19.2	706
51.13	707	(% style="color:#037691" %)AT+ATDC=xx.
19.2	708
51.2	709	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	710
	711
51.13	712	* (% style="color:blue" %)Downlink Payload (prefix 0xB1):
19.2	713
51.13	714	(% style="color:#037691" %)0xB1 00 00 3C (%%) ~/~/ Same as AT+ATDC=60000
19.2	715
	716
	717
57.1	718	=== 3.2.3 Set Transport Mode Packet transmission interval ===
50.2	719
	720
57.1	721	Set Transport Mode packet transmit interval
19.2	722
51.13	723	* (% style="color:blue" %)AT Command:
19.2	724
51.13	725	(% style="color:#037691" %)AT+MTDC=xx.
19.2	726
57.1	727	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	728
	729
51.13	730	* (% style="color:blue" %)Downlink Payload (prefix 0x03):
19.2	731
51.13	732	(% style="color:#037691" %)0x03 00 01 2C (%%) ~/~/ Same as AT+ MTDC=3000000
19.2	733
	734
	735
50.2	736	=== 3.2.4 Exit Alarm ===
19.2	737
50.2	738
19.2	739	Server send downlink command to exit Alarm mode
	740
51.13	741	* (% style="color:blue" %)AT Command: No AT Command
19.2	742
51.13	743	* (% style="color:blue" %)Downlink Payload (prefix 0x02):
19.2	744
51.13	745	(% style="color:#037691" %)0x02 01 (%%) ~/~/ Exit Alarm Mode
19.2	746
51.13	747
	748
50.2	749	=== 3.2.5 Disable/Enable LED flash ===
	750
	751
19.2	752	Disable/Enable LED for position, downlink and uplink
	753
51.13	754	* (% style="color:blue" %)AT Command:
19.2	755
51.13	756	(% style="color:#037691" %)AT+LON=xx. (Disable (0), Enable (1), default:1)
19.2	757
51.28	758	Example: AT+LON=0 ~-~-> Disable LED for position, downlink and uplink.
19.2	759
	760
51.13	761	* (% style="color:blue" %)Downlink Payload (prefix 0xAE):
19.2	762
51.13	763	(% style="color:#037691" %)0xAE 00 (%%) ~/~/ Same as AT+LON=0
19.2	764
	765
	766
59.1	767	=== 3.2.6 Disable/Enable Transport Mode ===
19.2	768
	769
59.1	770	Users can use this feature to enable/disable Transport Mode.
19.2	771
51.13	772	* (% style="color:blue" %)AT Command:
19.2	773
51.13	774	(% style="color:#037691" %)AT+INTWK=xx. (Disable (0), Enable (1), default:0)
19.2	775
59.1	776	Example: AT+ INTWK =1 ~-~-> Enable Transport Mode.
19.2	777
	778
51.13	779	* (% style="color:blue" %)Downlink Payload (prefix 0xAF):
19.2	780
51.13	781	(% style="color:#037691" %)0xAF 01 (%%) ~/~/ Same as AT+ INTWK =1
19.2	782
	783
	784
50.2	785	=== 3.2.7 Set Positioning Mode ===
19.2	786
50.2	787
79.1	788	SMOD define how TrackerD scan and uplink data:
19.2	789
	790
51.13	791	* (% style="color:blue" %)AT Command:
19.2	792
74.5	793	(% style="color:#037691" %)AT+SMOD=aa,bb,cc
19.2	794
60.2	795	(% style="color:#037691" %) aa:
19.2	796
74.5	797	* (% style="color:red" %)1: GPS ONLY(Factory Settings): (%%)only get and uplink GPS location info.
	798	* (% style="color:red" %)2: BLE ONLY: (%%)Only obtain iBeacon info via BLE and uplink. Design for Indoor tracking.
	799	* (% 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	800
	801	(% style="color:#037691" %)bb:
	802
74.5	803	* (% style="color:red" %)0 : (%%)GPS+ BAT+ State+Tem&Hum
	804	* (% style="color:red" %)1 :(%%) GPS +BAT State
60.2	805
74.5	806	(% style="color:#037691" %)cc:
60.2	807
74.5	808	* (% style="color:red" %)1 : (%%) (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State
60.2	809
74.5	810	(% style="color:blue" %)Example:
19.2	811
79.1	812	AT+ SMOD =1,0,0 ~-~-> GPS+ BAT+ State+Tem&Hum
74.5	813	AT+ SMOD =1,1,0 ~-~-> GPS +BAT State
	814	AT+ SMOD =2,0,1 ~-~-> (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State
19.2	815
	816
51.13	817	* (% style="color:blue" %)Downlink Payload (prefix 0xA5):
19.2	818
74.5	819	(% style="color:#037691" %)0xA5 01 00 00 (%%) ~/~/ Same as AT+ SMOD =1,0,0
19.2	820
	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
	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.
	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
	844
68.4	845	=== 3.2.9 Set PDOP value for GPS fix accuracy ===
19.2	846
	847
50.2	848	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	849
50.2	850
19.2	851	A GPS packet with lower PDOP has higher accuracy. PDOP default value is 2.0
	852
	853
51.13	854	* (% style="color:blue" %)AT Command:
19.2	855
51.13	856	(% style="color:#037691" %)AT+PDOP=2.5 (%%) ~-~-> Set PDOP to 2.5
19.2	857
	858
51.13	859	* (% style="color:blue" %)Downlink Payload (prefix 0xAD):
19.2	860
51.13	861	(% style="color:#037691" %)0xAD 00 0A (%%) ~/~/ Set AT+PDOP=1 (0x0A / 10 =1)
19.2	862
51.13	863	(% style="color:#037691" %)0xAD 00 19 (%%) ~/~/ Set AT+PDOP=2.5 (0x19 / 10 =2.5)
19.2	864
51.13	865	(% style="color:#037691" %)0xAD 00 46 (%%) ~/~/ Set AT+PDOP=7 (0x46 / 10 =7)
19.2	866
50.2	867
51.12	868
19.2	869	Disable/Enable the confirmation mode
	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
51.2	878	AT+ CFM=0 ~-~-> Disable confirmation
19.2	879
50.2	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
51.13	885	(% style="color:#037691" %)0x05 01 (%%) ~/~/ Same as AT+ SMOD =1
19.2	886
	887
	888
74.6	889	=== 3.2.10 Auto Send None-ACK messages ===
	890
	891
	892	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.
	893
	894
	895	* (% style="color:blue" %)AT Command: AT+PNACKMD
	896
	897	The default factory setting is 0.
	898
	899
	900	Command Example Function Response:
	901
	902	(% style="color:#037691" %)AT+PNACKMD=1 (%%) ~/~/ Poll None-ACK message OK
	903
	904
	905	* (% style="color:blue" %)Downlink Command: 0x34
	906
	907	Example: 0x3401 ~/~/ Same as AT+PNACKMD=1
	908
	909
84.2	910
80.1	911	=== 3.2.11 Set BLEMASK to filter BLE iBeacon ===
	912
84.2	913
80.1	914	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.
	915
84.5	916	(% style="color:red" %)Note: BLEMASK range is 6 ~~ 10 bytes. If AT+BLEMASK < 6 bytes, BLEMASK will be disabled.
80.1	917
84.5	918	(% style="color:blue" %)AT Command:
80.1	919
84.5	920	(% style="color:#037691" %)AT+BLEMASK=123456 (%%) ~/~/ Set BLEMASK = 123456
80.1	921
84.5	922	(% style="color:#037691" %)AT+BLEMASK=0 (%%) ~/~/ disable BLEMASK
80.1	923
	924
84.5	925	(% style="color:blue" %)Downlink Payload: (Prefix : 0xA5)
80.1	926
84.5	927	Example: 0xA5010203040506 ~/~/ Set BLEMASK to 123456
	928
	929
	930
19.4	931	= 4. Setting for Different Scenarios =
19.2	932
	933
	934
19.4	935	= 5. Upload Firmware =
19.2	936
19.4	937
	938	== 5.1 Firmware Change Log ==
	939
50.2	940
19.2	941	[[See this link>>url:https://github.com/dragino/TrackerD]]
	942
	943
50.2	944
19.4	945	== 5.2 How to upgrade firmware ==
19.2	946
	947
50.2	948	User can use the TrackerD's USB port to upgrade firmware into it. The hardware connection for upgrade firmware is as below:
19.2	949
	950
50.2	951	(% style="color:blue" %)Step1: (%%)Connect TrackerD and PC via USB cable shipped with TrackerD.
19.2	952
50.2	953
	954	(% style="color:blue" %)Step2: (%%) Install CH9102 driver in the PC.
	955
19.2	956	After installation of the driver and plug in TrackerD, user should be able to see com port in PC's device manager.
	957
	958
51.28	959	(% 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	960
	961
50.2	962	(% style="color:blue" %)Step4: (%%) Run Flash Download Tool and configure chip type to ESP32
19.2	963
	964
50.2	965	[[image:1664503563660-578.png]]
19.2	966
	967
50.2	968	[[image:1664503574618-659.png]]
19.2	969
50.2	970
84.2	971
50.2	972	(% style="color:blue" %)Step5: (%%) Select the firmware file (.bin format), com port and proper SPI configure. Clink Start. Bin file location:
	973
73.1	974	[[https:~~/~~/github.com/dragino/TrackerD/releases>>https://github.com/dragino/TrackerD/releases]]
19.2	975
	976
	977	Users need to use below files:
	978
	979	boot_app0.bin @0e000
	980
	981	ESP_LORA-eeprom-class.bin @ 0x10000
	982
	983
50.2	984	[[image:1664503593459-435.png]]
19.2	985
	986
	987
50.2	988	After upgrade finish, it will show finish as below:
19.2	989
50.2	990	[[image:1664503611848-385.png]]
19.2	991
	992
50.2	993
19.4	994	= 6. Developer Guide =
19.2	995
	996
19.4	997	== 6.1 Compile Source Code ==
	998
	999
	1000	=== 6.1.1 Set up ARDUINO compile environment ===
	1001
	1002
51.28	1003	* 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	1004
51.15	1005	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	1006
	1007
50.2	1008	[[image:1664503635019-941.png]]
19.2	1009
50.2	1010
68.4	1011
51.28	1012	* (% style="color:#037691" %)Go to tools ~-~-> Boards ~-~-> Boards Manager,(%%) find the esp32 information and install it.
19.2	1013
50.2	1014	[[image:1664503715811-892.png]]
19.2	1015
	1016
84.3	1017	(% 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	1018
84.3	1019	[[image:image-20221024105643-1.png]]
	1020
84.4	1021	~ Figure1
84.3	1022
	1023
	1024	[[image:image-20221024105643-2.png]]
	1025
84.4	1026	Figure2
84.3	1027
	1028
51.28	1029	* Download the latest TrackerD from the dragino github: [[https:~~/~~/github.com/dragino/TrackerD>>url:https://github.com/dragino/TrackerD]]
19.2	1030
50.2	1031	Put the Library in the TrackerD directory into the libraries file in the Arduino directory:
19.2	1032
	1033
50.2	1034	[[image:1664503752288-974.png]]
19.2	1035
50.2	1036
	1037
19.4	1038	== 6.2 Source Code ==
	1039
	1040
51.16	1041	* (% style="color:blue" %)Open the example in the TrackerD file, please select the correct port in the IDE, as shown below:
19.2	1042
50.2	1043	[[image:1664503794261-827.png]]
19.2	1044
	1045
	1046
51.16	1047	* (% style="color:blue" %)Click to upload
19.2	1048
50.2	1049	[[image:1664503808294-336.png]]
19.2	1050
	1051
	1052
51.16	1053	* (% style="color:blue" %)Check the result, if the upload is successful, as shown below, open the serial port to view the data
19.2	1054
50.2	1055	[[image:1664503824081-592.png]] [[image:1664503831430-500.png]]
19.2	1056
	1057
	1058
18.2	1059	= 7. FAQ =
15.2	1060
	1061
18.2	1062	== 7.1 How to change the LoRa Frequency Bands/Region? ==
14.1	1063
	1064
51.14	1065	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	1066
12.1	1067
2.1	1068
18.2	1069	== 7.2 What is the pin mapping for the USB program cable? ==
2.1	1070
7.1	1071
18.2	1072	[[image:1664499635206-262.png]]
7.1	1073
	1074
	1075
51.28	1076	(% border="1.5" cellspacing="3" style="background-color:#ffffcc; color:green; width:314px" %)
51.27	1077	\|=(% style="width: 118px;" %)Pin\|=(% style="width: 67px;" %)Color\|=(% style="width: 123px;" %)USB Pin
18.2	1078	\|(% style="width:118px" %)A4,B4,A9,B9\|(% style="width:67px" %)Red\|(% style="width:123px" %)VCC
	1079	\|(% style="width:118px" %)A7,B7\|(% style="width:67px" %)White\|(% style="width:123px" %)D- (N/A)
	1080	\|(% style="width:118px" %)A6,B6\|(% style="width:67px" %)Green\|(% style="width:123px" %)D+(N/A)
	1081	\|(% style="width:118px" %)A1,B1,A12,B12\|(% style="width:67px" %)Black\|(% style="width:123px" %)GND
	1082	\|(% style="width:118px" %)A5\|(% style="width:67px" %)Purple\|(% style="width:123px" %)MTDC/GOIO13
	1083	\|(% style="width:118px" %)B5\|(% style="width:67px" %)Blue\|(% style="width:123px" %)MTDC/GPIO12
	1084	\|(% style="width:118px" %)A8\|(% style="width:67px" %)Yellow\|(% style="width:123px" %)MTMS/GPIO14
	1085	\|(% style="width:118px" %)B8\|(% style="width:67px" %)Grey\|(% style="width:123px" %)MTDO/GPIO15
7.1	1086
84.19	1087
	1088
18.2	1089	= 8. Order Info =
7.1	1090
	1091
15.6	1092	Part Number: (% style="color:blue" %)TrackerD-XXX
8.1	1093
15.6	1094	(% style="color:blue" %)XXX(%%): The default frequency band
8.1	1095
15.6	1096	* (% style="color:red" %)EU433(%%): Default frequency band EU433
	1097	* (% style="color:red" %)EU868(%%): Default frequency band EU868
	1098	* (% style="color:red" %)IN865(%%): Default frequency band IN865
	1099	* (% style="color:red" %)KR920(%%): Default frequency band KR920
	1100	* (% style="color:red" %)AS923(%%): Default frequency band AS923
	1101	* (% style="color:red" %)AU915(%%): Default frequency band AU915
	1102	* (% style="color:red" %)US915(%%): Default frequency band US915
15.2	1103
84.19	1104
	1105
18.2	1106	= 9. Packing Info =
	1107
	1108
51.30	1109	(% style="color:#037691" %)Package Includes:
8.1	1110
50.3	1111	* TrackerD LoRaWAN GPS/BLE Tracker x 1
	1112	* USB recharge & program cable x 1
12.1	1113
51.30	1114	(% style="color:#037691" %)Dimensions and Weight:
12.1	1115
50.3	1116	* Device Size: 85 x 48 x 15 cm
	1117	* Weight: 50g
15.6	1118
84.19	1119
	1120
18.2	1121	= 10. Support =
	1122
50.3	1123
18.2	1124	* 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	1125	* 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	1126
84.19	1127
	1128
18.2	1129	= 11. Reference =
	1130
	1131
12.1	1132	* [[Firmware in Bin format>>https://www.dropbox.com/sh/733s8xlwahhqg1d/AABxDz80lBVX_to8zNuUQWFja?dl=0]]
	1133	* [[Source Code>>https://github.com/dragino/TrackerD]]
	1134	* [[Hardware Source>>https://www.dropbox.com/sh/orwoy6cecb89m4e/AAD37sRuUrvKsHgAJxuVTkB5a?dl=0]]
51.28	1135
68.2	1136

Wiki source code of TrackerD -LoRaWAN Tracker User Manual

Applications