Wiki source code of TrackerD -LoRaWAN Tracker User Manual

Version 79.1 by Edwin Chen on 2022/10/22 00:11

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

Wiki source code of TrackerD -LoRaWAN Tracker User Manual

Applications