Wiki source code of TrackerD -LoRaWAN Tracker User Manual

Version 84.13 by Xiaoling on 2022/10/26 08:59

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

Wiki source code of TrackerD -LoRaWAN Tracker User Manual

Applications