Wiki source code of TrackerD -LoRaWAN Tracker User Manual

Version 84.11 by Xiaoling on 2022/10/26 08:50

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

Wiki source code of TrackerD -LoRaWAN Tracker User Manual

Applications