Wiki source code of TrackerD -LoRaWAN Tracker User Manual

Version 51.20 by Xiaoling on 2022/09/30 14:43

version	line-number	content
51.2	1	(% style="text-align:center" %)
	2	[[image:1664505654417-133.png]]
	3
	4
	5
	6
7.1	7	(% class="wikigeneratedid" %)
	8	Table of Contents:
1.1	9
51.2	10	{{toc/}}
1.1	11
2.1	12
	13
12.1	14
15.2	15	= 1. Introduction =
	16
	17
50.2	18	== 1.1 What is TrackerD ==
15.2	19
50.2	20
15.3	21	(((
	22	TrackerD is an (% style="color:blue" %)Open Source LoRaWAN Tracker(%%) based on (% style="color:blue" %)ESP32 MCU(%%) and (% style="color:blue" %)Semtech LoRa Wireless Chip.
	23	)))
7.2	24
15.3	25	(((
19.2	26	In TrackerD, there are various sensors such as GPS, WiFi, BLE, Temperature, Humidity, Motion Detection, and Buzzer. User can use TrackerD for different tracking scenario.
7.2	27
51.18	28	(((
8.1	29	TrackerD is program friendly. Developers can use Arduino IDE to customize the software of TrackerD to fit their IoT solution.
51.18	30	)))
8.1	31
51.18	32	(((
19.2	33	The LoRa wireless technology used in TrackerD allows the user to send data and reach extremely long ranges at low data-rates. It provides ultra-long range spread spectrum communication and high interference immunity whilst minimizing current consumption. It targets professional tracking services.
15.3	34	)))
51.18	35	)))
8.1	36
15.3	37	(((
	38	TrackerD is equipped with a (% style="color:blue" %)1000mAh Li-on rechargeable battery(%%). Each TrackerD has a worldwide unique OTAA keys to join the LoRaWAN network.
16.4	39
	40
15.3	41	)))
8.1	42
19.2	43	[[image:1664499921684-770.png]]
8.1	44
15.4	45
19.2	46	(% style="color:red" %)Note: LoRaWAN server can be a general LoRaWAN server other than TTN.
8.1	47
15.2	48
50.2	49
19.2	50	== 1.2 Specifications ==
12.1	51
15.2	52
19.2	53	(% style="color:blue" %)Micro Controller:
15.2	54
19.2	55	* Espressif ESP32 PICO D4
	56	* MCU: ESP32 PICO D4
	57	* Bluetooth: Bluetooth V4.2 BR/EDR and Bluetooth LE
	58	* WiFi : 802.11 b/g/n (802.11n up to 150 Mbps)
	59	* Integrated SPI flash : 4 MB
	60	* RAM: 448 KB
	61	* EEPROM: 520 KB
	62	* Clock Speed: 32Mhz
	63
51.18	64
	65
19.2	66	(% style="color:blue" %)Common DC Characteristics:
	67
	68	* Supply Voltage: 5V via USB port or Internal li-on battery
	69	* Operating Temperature: -40 ~~ 60°C
	70
51.18	71
	72
19.2	73	(% style="color:blue" %)LoRa Spec:
	74
	75	* Frequency Range,
	76	** Band 1 (HF): 862 ~~ 1020 Mhz
	77	* 168 dB maximum link budget.
	78	* +20 dBm - 100 mW constant RF output vs.
	79	* +14 dBm high efficiency PA.
	80	* Programmable bit rate up to 300 kbps.
	81	* High sensitivity: down to -148 dBm.
	82	* Bullet-proof front end: IIP3 = -12.5 dBm.
	83	* Excellent blocking immunity.
	84	* Low RX current of 10.3 mA, 200 nA register retention.
	85	* Fully integrated synthesizer with a resolution of 61 Hz.
	86	* FSK, GFSK, MSK, GMSK, LoRaTM and OOK modulation.
	87	* Built-in bit synchronizer for clock recovery.
	88	* Preamble detection.
	89	* 127 dB Dynamic Range RSSI.
	90	* Automatic RF Sense and CAD with ultra-fast AFC.
	91	* Packet engine up to 256 bytes with CRC.
	92	* LoRaWAN 1.0.3 Specification
	93
51.18	94
	95
19.2	96	(% style="color:blue" %)Battery:
	97
	98	* 1000mA Li-on Battery power (for model TrackerD)
	99
51.18	100
	101
19.2	102	(% style="color:blue" %)Power Consumption
	103
	104	* Sleeping Mode: 200uA
	105	* LoRa Transmit Mode: 125mA @ 20dBm 44mA @ 14dBm
	106	* Tracking: max: 38mA
	107
51.18	108
	109
	110
19.2	111	== 1.3 Features ==
	112
	113
	114	* LoRaWAN 1.0.3 Class A
	115	* ESP32 PICO D4
	116	* SX1276/78 Wireless Chip
51.17	117	** Arduino IDE Compatible
19.2	118	* Open source hardware / software
	119	* Regular/ Real-time GPS,BLE,WIFI tracking
	120	* Built-in3 axis accelerometer (LIS3DH)
	121	* Humidity / temperature sensor : GXCAS Technology GXHT3X
	122	* Motion sensing capability
	123	* Power Monitoring
	124	* Charging circuit via USB port
	125	* 1000mA Li-on Battery power
	126	* Tri-color LED, Alarm button
	127	* Datalog
	128
51.18	129
	130
	131
19.2	132	== 1.4 Applications ==
	133
	134
12.1	135	* Logistics and Supply Chain Management
	136	* Human tracking
	137
51.18	138
	139
	140
19.3	141	= 2.1 Use TrackerD =
19.2	142
50.2	143
19.3	144	== 2.1 How it works? ==
19.2	145
19.3	146
19.2	147	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.
	148
	149
50.2	150
19.3	151	== 2.2 Quick guide to connect to LoRaWAN server ==
19.2	152
	153
50.2	154	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	155
	156
50.2	157	[[image:1664501652064-326.png]]
19.2	158
50.2	159
	160
19.2	161	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:
	162
	163
50.2	164	(% style="color:blue" %)Step 1:(%%) Create a device in TTN V3 with the OTAA keys from TrackerD.
	165
19.2	166	Each TrackerD is shipped with a sticker with the default device EUI as below:
	167
51.3	168
50.2	169	[[image:1664501677253-891.png]]
19.2	170
	171
	172	Input these keys to their LoRaWAN Server portal. Below is TTN V3 screen shot:
	173
	174
50.2	175	__Add APP EUI in the application:__
19.2	176
	177
50.2	178	[[image:1664501711466-918.png]]
19.2	179
	180
	181
50.2	182	[[image:1664501721248-725.png]]
19.2	183
	184
50.2	185	[[image:1664501734705-405.png]]
19.2	186
	187
	188
50.2	189	__Add APP KEY and DEV EUI:__
19.2	190
	191
50.2	192	[[image:1664501784668-703.png]]
19.2	193
	194
	195
	196
50.2	197	(% style="color:blue" %)Step 2:(%%) Power on TrackerD by using the on board switch.
19.2	198
50.2	199
	200	(% 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.
	201
	202
	203	(% style="color:blue" %)Positioning Mode(SMOD):
	204
51.9	205	* (% style="color:#037691" %)GPS ONLY(Factory Settings): (%%)only get GPS location info.
	206	* (% style="color:#037691" %)BLE ONLY: (%%)Only obtain iBeacon info via BLE. Design for Indoor tracking.
	207	* (% style="color:#037691" %)GPS/BLE Hybrid: (%%)Combination for Indoor and Outdoor tracking.
19.2	208
51.3	209	User can switch modes by [[changing SMOD>>\|\|anchor="H3.2.7SetPositioningMode"]].
19.2	210
	211
50.2	212
51.3	213	== 2.3 Uplink Payload ==
19.2	214
	215
50.2	216	=== 2.3.1 Uplink FPORT~=5, Device Status ===
19.2	217
	218
	219
51.3	220	=== 2.3.2 Uplink FPORT~= , Realtime GNSS Positioning ===
19.2	221
	222
50.2	223	The default uplink payload includes totally 11 bytes. (User can use AT+MOD=0 to enable the Temperature and humidity sensor to hum/tem info from accelerometer. When accelerometer info is enable, total payload will be 15 bytes, please note 15 bytes won't work on DR0 on US915/AU915 frequency band. )
19.2	224
50.2	225
51.19	226	(% border="1.5" cellspacing="3" style="background-color:#ffffcc; color:green; width:520px" %)
51.18	227	\|=(% scope="row" style="width: 69px;" %)(((
51.20	228	Size (bytes)
19.2	229
50.2	230	)))\|(% style="width:76px" %)4\|(% style="width:87px" %)4\|(% style="width:76px" %)2\|(% style="width:52px" %)1\|(% style="width:88px" %)(((
19.2	231	2
	232
	233	(optional )
50.2	234	)))\|(% style="width:83px" %)(((
19.2	235	2
	236
	237	(optional)
	238	)))
51.18	239	\|=(% style="width: 69px;" %)Value\|(% style="width:76px" %)[[Latitude>>\|\|anchor="HLocationinfo:"]]\|(% style="width:87px" %)[[Longitude>>\|\|anchor="HLocationinfo:"]]\|(% style="width:76px" %)(((
51.5	240	[[Alarm & BAT>>\|\|anchor="HAlarm26BAT:"]]
	241	)))\|(% style="width:52px" %)[[FLAG>>\|\|anchor="HFLAG:"]]\|(% style="width:88px" %)[[Hum>>\|\|anchor="HHum:"]]\|(% style="width:83px" %)[[Tem>>\|\|anchor="HTem:"]]
19.2	242
50.2	243	[[image:1664501958445-288.png]]
19.2	244
50.2	245
51.11	246	==== (% style="color:blue" %)Alarm & BAT:(%%) ====
19.2	247
50.2	248	(% border="2" style="background-color:#ffffcc; color:green; width:329px" %)
	249	\|(% style="width:72px" %)Size(bit)\|(% style="width:67px" %)1 bit\|(% style="width:118px" %)1bit\|(% style="width:63px" %)14 bits
51.7	250	\|(% style="width:72px" %)Value\|(% style="width:67px" %)reserve\|(% style="width:118px" %)Alarm Indicate\|(% style="width:63px" %)[[BAT>>\|\|anchor="HBAT:"]]
19.2	251
51.11	252	==== (% style="color:blue" %)FLAG:(%%) ====
50.2	253
	254	(% border="2" style="background-color:#ffffcc; color:green; width:332px" %)
	255	\|(% style="width:79px" %)Size(bit)\|(% style="width:55px" %)2 bits\|(% style="width:47px" %)1bit\|(% style="width:140px" %)5 bits
51.10	256	\|(% style="width:79px" %)Value\|(% style="width:55px" %)[[MOD>>\|\|anchor="H2.3.4BLEpositioningPayload28Fport229"]]\|(% style="width:47px" %)[[LON>>\|\|anchor="HLON:"]]\|(% style="width:140px" %)Firmware version
19.2	257
51.11	258	Example: Payload: 0x02863D68 FAC29BAF 4B45 60 0202 011A
19.2	259
	260
51.11	261	==== (% style="color:blue" %)Location info:(%%) ====
19.2	262
51.11	263	* Latitude: 02863D68 ⇒ //if (0x//02863D68//& 0x80000000 = 0 )~:// //value = 02863D68 /1000000 = 42.351976//
	264	* Longitude: FAC29BAF ⇒ //if (0x//FAC29BAF// & 0x80000000 = 1 )~:// //value = (0x//FAC29BAF// – 0x 100000000)/1000000 =//-87.9094//57//
19.2	265
51.9	266	(% style="color:red" %)Important note:
19.2	267
50.2	268	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	269
50.2	270	2. In firmware version v1.5, Roll & Pitch is disabled by default.
19.2	271
50.2	272	3. When enable 9-axis motion sensor, the total payload will be 15 bytes, while US915/AU915 DR0 accept only 11 bytes payload. In this case, the payload on server will be ignore and shows as below:
19.2	273
	274
50.2	275	[[image:1664502116362-706.png]]
19.2	276
	277
50.2	278
	279	4. While GPS can't get location info after timeout(FTIME Parameter), the latitude and longitude will be filled with all 0x00:
	280
	281	[[image:1664502166010-515.png]]
	282
	283
	284
51.11	285	==== (% style="color:blue" %)Alarm:(%%) ====
50.2	286
51.9	287
51.6	288	Example: 0x4B & 0x40 >> 6 = 0x01
19.2	289
	290
51.11	291	==== (% style="color:blue" %)BAT:(%%) ====
51.6	292
51.9	293
51.6	294	Example: 0x0CDD & 0x3FFF ⇒ 3293 (mV).
	295
51.9	296	The battery info shows the current voltage, for (% style="color:blue" %)TrackerD(%%) version which powered by li-on battery. User can use below mapping to indicate the battery in percentage: \
51.6	297
	298
50.4	299	* > 4.0v : 80% ~~ 100%
	300	* 3.85v ~~3.99v: 60% ~~ 80%
	301	* 3.70v ~~ 3.84v: 40% ~~ 60%
	302	* 3.40v ~~ 3.69v: 20% ~~ 40%
	303	* < 3.39v: 0~~20%
19.2	304
51.11	305	==== (% style="color:blue" %)LON:(%%) ====
	306
51.9	307
51.4	308	Enable/Disable LED activity for uplink
19.2	309
50.2	310	0x00: Disable LED indicator.
19.2	311
50.2	312	0x01: Enable LED indicator (Default Value)
19.2	313
	314
51.11	315	==== (% style="color:blue" %)Hum:(%%) ====
19.2	316
51.4	317	0202 = //if (0x0202 & 0x8000 = 0 ): value =// 0x0202 / 100 = +514 ⇒ 51.4 degree
19.2	318
	319
51.11	320	==== (% style="color:blue" %)Tem:(%%) ====
19.2	321
51.9	322	011A =if (0x011A & 0x8000 = 1 ): value =( 0x011A - 0x10000)/10(dec) ⇒ -//28.2 degree//
51.4	323
	324
	325
	326
50.2	327	=== 2.3.3 Uplink FPORT~= , History GNSS Positioning ===
19.2	328
	329
50.2	330
	331	=== 2.3.4 BLE positioning Payload(Fport2) ===
	332
	333
19.2	334	Different MODE has different payload:
	335
	336	MODE=2
	337
51.11	338	(% border="2" style="background-color:#ffffcc; color:green; width:491px" %)
50.2	339	\|(% style="width:70px" %)(((
19.2	340	Size
	341
	342	(bytes)
51.11	343	)))\|(% style="width:44px" %)16\|(% style="width:61px" %)4\|(% style="width:63px" %)4\|(% style="width:71px" %)2\|(% style="width:50px" %)4\|(% style="width:47px" %)2\|(% style="width:15px" %)1
	344	\|(% style="width:70px" %)Value\|(% style="width:44px" %)[[UUID>>\|\|anchor="HLocationinfo:"]]\|(% style="width:61px" %)(((
51.8	345	iBeacon MAJOR
51.11	346	)))\|(% style="width:63px" %)(((
	347	iBeacon MINOR
50.2	348	)))\|(% style="width:71px" %)(((
51.8	349	iBeacon Measured Power
51.11	350	)))\|(% style="width:50px" %)(((
51.8	351	iBeacon RSSI
51.11	352	)))\|(% style="width:47px" %)(((
51.8	353	[[Alarm & BAT>>\|\|anchor="HAlarm26BAT:"]]
51.11	354	)))\|(% style="width:15px" %)[[FLAG>>\|\|anchor="HFLAG:"]]
19.2	355
50.2	356	[[image:1664502425687-834.png]]
19.2	357
	358
51.9	359	* (% style="color:#037691" %)BAT: (%%) Ex1: 0x4B45 & 0x3FFF ⇒ 3901 (mV).
	360	* (% style="color:#037691" %)MODE: (%%)Define the payload format.
	361	* (% style="color:#037691" %)UUID: (%%)The uuid from the strongest iBeacon.
	362	* (% style="color:#037691" %)MAJOR: (%%) The MAJOR from the strongest iBeacon.
	363	* (% style="color:#037691" %)MINOR: (%%)The MAJOR from the strongest iBeacon.
	364	* (% style="color:#037691" %)Measured Power: (%%) The Measured Power from the strongest iBeacon.
	365	* (% style="color:#037691" %)RSSI: (%%) The RSSI from the strongest iBeacon.
19.2	366
19.3	367	=== 2.3.5 Add Payload format in TTN V3 ===
	368
50.2	369
19.2	370	In TTN V3, use can add a custom payload so it shows friendly.
	371
51.9	372	In the page (% style="color:#037691" %)Applications ~-~-> Payload Formats ~-~-> Custom ~-~-> decoder
19.2	373
	374
50.2	375	[[image:1664502649601-895.png]]
	376
51.9	377
19.2	378	Add the decoder from this link:
	379
	380
	381	Save the change the uplink message will be parsed. As below:
	382
50.2	383	[[image:1664502676891-606.png]]
19.2	384
	385
	386
19.3	387	== 2.4 Integrate with Datacake ==
19.2	388
	389
	390	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.
	391
50.2	392	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	393
	394
50.2	395	[[image:1664502695771-538.png]]
19.2	396
50.2	397
	398
19.3	399	== 2.5 Integrate with Tago ==
19.2	400
	401
	402	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.
	403
	404	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]]
	405
	406
50.2	407	[[image:1664502715371-321.png]]
19.2	408
	409
	410
19.3	411	== 2.6 Alarm Mode ==
19.2	412
	413
51.11	414	User can push the (% style="color:red" %)RED button(%%) by more than 5 seconds to enter Alarm Mode.
19.2	415
	416
51.11	417	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.
19.2	418
	419
	420	Two ways to exit alarm mode:
	421
	422	* Server send a downlink command to exit.
	423	* User fast press the RED button 10 times.
	424
51.11	425	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.
19.2	426
	427
50.2	428
19.3	429	== 2.7 Sports Mode ~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-- ==
19.2	430
	431
	432
19.3	433	== 2.8 LED Status ==
19.2	434
	435
50.2	436	(% border="2" style="background-color:#ffffcc; color:green; width:636px" %)
	437	\|(% style="width:157px" %)Event\|(% style="width:271px" %)Action\|(% style="width:202px" %)AT+LON to control on/off
51.11	438	\|(% 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
	439	\|(% style="width:157px" %)Join request\|(% style="width:271px" %)(% style="color:green" %)Green (%%)led fast blink once (200ms)\|(% style="width:202px" %)Yes
	440	\|(% style="width:157px" %)Join Success\|(% style="width:271px" %)(% style="color:green" %)Green(%%) led on 5 second\|(% style="width:202px" %)N/A
	441	\|(% style="width:157px" %)Fixing Location\|(% style="width:271px" %)(% style="color:blue" %)BLUE (%%)blinks 200ms per second\|(% style="width:202px" %)Yes
	442	\|(% style="width:157px" %)Fixed and uplink\|(% style="width:271px" %)(% style="color:green" %)GREEN (%%)blinks twice (200ms per blink)\|(% style="width:202px" %)Yes
	443	\|(% style="width:157px" %)Fail Fix and uplink\|(% style="width:271px" %)(% style="color:red" %)RED (%%)blinks twice (200ms per blink)\|(% style="width:202px" %)Yes
	444	\|(% style="width:157px" %)Enter Alarm mode\|(% style="width:271px" %)(% style="color:red" %)RED (%%)on for 3 seconds\|(% style="width:202px" %)Yes
	445	\|(% style="width:157px" %)Uplink under Alarm\|(% style="width:271px" %)(% style="color:red" %)RED (%%)on for 1 second\|(% style="width:202px" %)Yes
	446	\|(% style="width:157px" %)Exit Alarm\|(% style="width:271px" %)(% style="color:blue" %)BLUE (%%)led on 5 second\|(% style="width:202px" %)Yes
	447	\|(% style="width:157px" %)Get Downlink\|(% style="width:271px" %)(% style="color:green" %)GREEN(%%) led on 1 second\|(% style="width:202px" %)Yes
	448	\|(% style="width:157px" %)Movement Detect\|(% style="width:271px" %)(% style="color:red" %)RED (%%)led on 500ms\|(% style="width:202px" %)N/A
19.2	449
19.3	450	== 2.9 Button Function ==
19.2	451
50.2	452
51.11	453	(% style="color:green" %)RESET button:
19.2	454
50.2	455	[[image:1664502835802-546.png]]
19.2	456
	457	Push this button will reboot the device. Device will exit alarm mode and re-join to LoRaWAN server.
	458
	459
51.11	460	(% style="color:red" %)RED button:
19.2	461
50.2	462	[[image:1664502854406-763.png]]
19.2	463
	464
50.2	465	(% border="2" style="background-color:#ffffcc; color:green; width:627px" %)
	466	\|(% style="width:135px" %)Function\|(% style="width:220px" %)Action\|(% style="width:265px" %)Description
51.11	467	\|(% 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"]]
	468	\|(% 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	469	\|(% 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	470
51.13	471
	472
19.3	473	== 2.10 USB Port Function ==
19.2	474
50.2	475
19.2	476	The USB interface of TrackerD has below functions:
	477
	478	* Power on the device
	479	* Recharge the battery
51.11	480	* [[Configure Device>>\|\|anchor="H3.ConfigureTrackerDviaATcommandorLoRaWANdownlink"]]
	481	* [[Upgrade Firmware>>\|\|anchor="H5.UploadFirmware"]]
19.2	482
	483
51.11	484
19.3	485	= 3. Configure TrackerD via AT command or LoRaWAN downlink =
19.2	486
	487
	488	User can configure TrackerD via AT Command or LoRaWAN Downlink.
	489
51.13	490	LoRaWAN Downlink instruction for different platforms: [[IoT LoRaWAN Server>>doc:Main.WebHome]]
19.2	491
	492
50.2	493
19.3	494	== 3.1 Access AT Command ==
19.2	495
	496
50.2	497	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	498
	499
50.2	500	[[image:1664502999401-486.png]]
	501
	502
51.11	503	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	504
	505
50.2	506	[[image:1664503022490-662.png]]
19.2	507
	508
	509
50.2	510	[[image:1664503035713-500.png]]
19.2	511
	512
	513
50.2	514	[[image:1664503047675-651.png]]
	515
	516
	517
19.3	518	== 3.2 Command Set ==
19.2	519
	520
19.3	521	=== 3.2.1 Set Transmit Interval ===
19.2	522
50.2	523
19.2	524	Set device uplink interval.
	525
51.13	526	* (% style="color:blue" %)AT Command:
19.2	527
51.13	528	(% style="color:#037691" %)AT+TDC=xxx
19.2	529
50.2	530	Example: AT+TDC=300000. Means set interval to 5 minutes(300 seconds)
19.2	531
	532
51.13	533	* (% style="color:blue" %)Downlink Payload (prefix 0x01):
19.2	534
51.13	535	(% style="color:#037691" %)0x01 00 01 2C (%%) ~/~/ Same as AT+TDC=300000
19.2	536
	537
50.2	538
19.3	539	=== 3.2.2 Set Alarm Packet transmission interval ===
19.2	540
50.2	541
19.2	542	Set alarm packet transmit interval
	543
51.13	544	* (% style="color:blue" %)AT Command:
19.2	545
51.13	546	(% style="color:#037691" %)AT+ATDC=xx.
19.2	547
51.2	548	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	549
	550
51.13	551	* (% style="color:blue" %)Downlink Payload (prefix 0xB1):
19.2	552
51.13	553	(% style="color:#037691" %)0xB1 00 00 3C (%%) ~/~/ Same as AT+ATDC=60000
19.2	554
	555
	556
50.2	557	=== 3.2.3 Set Sports Mode Packet transmission interval ===
	558
	559
19.2	560	Set sports packet transmit interval
	561
51.13	562	* (% style="color:blue" %)AT Command:
19.2	563
51.13	564	(% style="color:#037691" %)AT+MTDC=xx.
19.2	565
51.2	566	Example: AT+MTDC=300000 ~-~-> Set Sports Mode Packet Interval to 300 seconds. TrackerD will send every 300 seconds in Sports mode, Default Value: 300000
19.2	567
	568
51.13	569	* (% style="color:blue" %)Downlink Payload (prefix 0x03):
19.2	570
51.13	571	(% style="color:#037691" %)0x03 00 01 2C (%%) ~/~/ Same as AT+ MTDC=3000000
19.2	572
	573
	574
50.2	575	=== 3.2.4 Exit Alarm ===
19.2	576
50.2	577
19.2	578	Server send downlink command to exit Alarm mode
	579
51.13	580	* (% style="color:blue" %)AT Command: No AT Command
19.2	581
	582
51.13	583	* (% style="color:blue" %)Downlink Payload (prefix 0x02):
19.2	584
51.13	585	(% style="color:#037691" %)0x02 01 (%%) ~/~/ Exit Alarm Mode
19.2	586
51.13	587
	588
50.2	589	=== 3.2.5 Disable/Enable LED flash ===
	590
	591
19.2	592	Disable/Enable LED for position, downlink and uplink
	593
51.13	594	* (% style="color:blue" %)AT Command:
19.2	595
51.13	596	(% style="color:#037691" %)AT+LON=xx. (Disable (0), Enable (1), default:1)
19.2	597
50.2	598	Example: AT+LON=0 ~-~-> Disable LED for position, downlink and uplink.
19.2	599
	600
51.13	601	* (% style="color:blue" %)Downlink Payload (prefix 0xAE):
19.2	602
51.13	603	(% style="color:#037691" %)0xAE 00 (%%) ~/~/ Same as AT+LON=0
19.2	604
	605
	606
50.2	607	=== 3.2.6 Disable/Enable movement detect (Debug Only) ===
19.2	608
	609
	610	User can use this feature to check and set thread hole of movement detect
	611
51.13	612	* (% style="color:blue" %)AT Command:
19.2	613
51.13	614	(% style="color:#037691" %)AT+INTWK=xx. (Disable (0), Enable (1), default:0)
19.2	615
51.2	616	Example: AT+ INTWK =1 ~-~-> Enable detect movement.
19.2	617
	618
51.13	619	* (% style="color:blue" %)Downlink Payload (prefix 0xAF):
19.2	620
51.13	621	(% style="color:#037691" %)0xAF 01 (%%) ~/~/ Same as AT+ INTWK =1
19.2	622
	623
	624
50.2	625	=== 3.2.7 Set Positioning Mode ===
19.2	626
50.2	627
19.2	628	SMOD define the how TrackerD scan and uplink date.
	629
50.2	630	GPS室外定位模式：设备默认模式，设备入网后会发送device当前模式下的信息，随后立即定位发送数据包（默认是3分钟定位，超过将发送无效数据），如果出现意外情况下，快速按键3下，将会发出报警消息（默认每分钟发送一次）。GPS还有一种logdata模式，在断网的情况下将数据存储下来，等到有网的时候，一次将数据以每10秒上报。
19.2	631
50.2	632	BLE室内定位模式：设备入网后会发送device当前模式下的信息，随后立即定位发送数据包（默认是5秒，超过将发送无效数据），如果出现意外情况下，快速按键3下，将会发出报警消息（默认每3分钟发送一次）。
19.2	633
50.2	634	GPS和BLE混动模式：设备入网后会发送device当前模式下的信息，随后立即判断是否在室内，如果是就进行BLE定位，不是就GPS定位。如果出现意外情况下，快速按键3下，将会发出报警消息（默认每分钟发送一次）。
19.2	635
50.2	636	运动模式：设备入网后会发送device当前模式下的信息，随后发送GPS定位数据，设备判断是否在运动，没有运动传感器没有检测到动作，立即进入静止状态（默认20分钟），如果产生运动，将每5分钟发送一次数据，再第五分钟后检测设备有误运动，无将切换到静止状态，有立即发送数据。
19.2	637
	638
	639
51.13	640	* (% style="color:blue" %)AT Command:
19.2	641
51.13	642	(% style="color:#037691" %)AT+SMOD=xx.
19.2	643
	644
50.2	645	Example:
19.2	646
50.2	647	AT+ SMOD =1,0 ~-~-> GPS+ BAT+ State+Tem&Hum
19.2	648
50.2	649	AT+ SMOD =1,1 ~-~-> GPS +BAT State
19.2	650
50.2	651	AT+ SMOD =2,3 ~-~-> (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State。
19.2	652
50.2	653
51.13	654	* (% style="color:blue" %)Downlink Payload (prefix 0xA5):
19.2	655
51.13	656	(% style="color:#037691" %)0xA5 01 00 (%%) ~/~/ Same as AT+ SMOD =1,0
19.2	657
	658
	659
50.2	660	=== 3.2.8 Set MAX GPS position time ===
	661
	662
19.2	663	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.
	664
	665
	666	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.
	667
	668
51.13	669	* (% style="color:blue" %)AT Command:
19.2	670
51.13	671	(% style="color:#037691" %)AT+FTIME=xx (%%) ~-~-> Set to use xx as max fix time.
19.2	672
50.2	673	Example: AT+FTIME=150
19.2	674
	675
51.13	676	* (% style="color:blue" %)Downlink Payload (prefix 0xAA):
19.2	677
51.13	678	(% style="color:#037691" %)0xAA 00 96 (%%) ~/~/ Set AT+FTIME=150
19.2	679
	680
	681
19.4	682	=== 3.3.9 Set PDOP value for GPS fix accuracy ===
19.2	683
	684
50.2	685	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	686
50.2	687
19.2	688	A GPS packet with lower PDOP has higher accuracy. PDOP default value is 2.0
	689
	690
51.13	691	* (% style="color:blue" %)AT Command:
19.2	692
51.13	693	(% style="color:#037691" %)AT+PDOP=2.5 (%%) ~-~-> Set PDOP to 2.5
19.2	694
	695
51.13	696	* (% style="color:blue" %)Downlink Payload (prefix 0xAD):
19.2	697
51.13	698	(% style="color:#037691" %)0xAD 00 0A (%%) ~/~/ Set AT+PDOP=1 (0x0A / 10 =1)
19.2	699
51.13	700	(% style="color:#037691" %)0xAD 00 19 (%%) ~/~/ Set AT+PDOP=2.5 (0x19 / 10 =2.5)
19.2	701
51.13	702	(% style="color:#037691" %)0xAD 00 46 (%%) ~/~/ Set AT+PDOP=7 (0x46 / 10 =7)
19.2	703
50.2	704
51.12	705
19.2	706	Disable/Enable the confirmation mode
	707
51.13	708	* (% style="color:blue" %)AT Command:
19.2	709
51.13	710	(% style="color:#037691" %)AT+CFM=xx.
19.2	711
	712
50.2	713	~ Example:
19.2	714
51.2	715	AT+ CFM=0 ~-~-> Disable confirmation
19.2	716
50.2	717	AT+ CFM=1 ~-~-> Enable confirmation
19.2	718
50.2	719
51.13	720	* (% style="color:blue" %)Downlink Payload (prefix 0x05):
19.2	721
51.13	722	(% style="color:#037691" %)0x05 01 (%%) ~/~/ Same as AT+ SMOD =1
19.2	723
	724
	725
19.4	726	= 4. Setting for Different Scenarios =
19.2	727
	728
	729
19.4	730	= 5. Upload Firmware =
19.2	731
19.4	732
	733	== 5.1 Firmware Change Log ==
	734
50.2	735
19.2	736	[[See this link>>url:https://github.com/dragino/TrackerD]]
	737
	738
50.2	739
19.4	740	== 5.2 How to upgrade firmware ==
19.2	741
	742
50.2	743	User can use the TrackerD's USB port to upgrade firmware into it. The hardware connection for upgrade firmware is as below:
19.2	744
	745
50.2	746	(% style="color:blue" %)Step1: (%%)Connect TrackerD and PC via USB cable shipped with TrackerD.
19.2	747
50.2	748
	749	(% style="color:blue" %)Step2: (%%) Install CH9102 driver in the PC.
	750
19.2	751	After installation of the driver and plug in TrackerD, user should be able to see com port in PC's device manager.
	752
	753
51.17	754	(% 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	755
	756
50.2	757	(% style="color:blue" %)Step4: (%%) Run Flash Download Tool and configure chip type to ESP32
19.2	758
	759
50.2	760	[[image:1664503563660-578.png]]
19.2	761
	762
50.2	763	[[image:1664503574618-659.png]]
19.2	764
50.2	765
	766	(% style="color:blue" %)Step5: (%%) Select the firmware file (.bin format), com port and proper SPI configure. Clink Start. Bin file location:
	767
19.2	768	[[https:~~/~~/www.dropbox.com/sh/733s8xlwahhqg1d/AABxDz80lBVX_to8zNuUQWFja?dl=0>>url:https://www.dropbox.com/sh/733s8xlwahhqg1d/AABxDz80lBVX_to8zNuUQWFja?dl=0]]
	769
	770
	771	Users need to use below files:
	772
	773	boot_app0.bin @0e000
	774
	775	ESP_LORA-eeprom-class.bin @ 0x10000
	776
	777
50.2	778	[[image:1664503593459-435.png]]
19.2	779
	780
	781
50.2	782	After upgrade finish, it will show finish as below:
19.2	783
50.2	784	[[image:1664503611848-385.png]]
19.2	785
	786
50.2	787
19.4	788	= 6. Developer Guide =
19.2	789
	790
19.4	791	== 6.1 Compile Source Code ==
	792
	793
	794	=== 6.1.1 Set up ARDUINO compile environment ===
	795
	796
50.2	797	* 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	798
51.15	799	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	800
	801
50.2	802	[[image:1664503635019-941.png]]
19.2	803
50.2	804
51.16	805	* (% style="color:#037691" %)Go to tools ~-~-> Boards ~-~-> Boards Manager,(%%) find the esp32 information and install it.
19.2	806
50.2	807	[[image:1664503715811-892.png]]
19.2	808
	809
	810
50.2	811	* Download the latest TrackerD from the dragino github: [[https:~~/~~/github.com/dragino/TrackerD>>url:https://github.com/dragino/TrackerD]]
19.2	812
50.2	813	Put the Library in the TrackerD directory into the libraries file in the Arduino directory:
19.2	814
	815
50.2	816	[[image:1664503752288-974.png]]
19.2	817
50.2	818
	819
19.4	820	== 6.2 Source Code ==
	821
	822
51.16	823	* (% style="color:blue" %)Open the example in the TrackerD file, please select the correct port in the IDE, as shown below:
19.2	824
50.2	825	[[image:1664503794261-827.png]]
19.2	826
	827
	828
51.16	829	* (% style="color:blue" %)Click to upload
19.2	830
50.2	831	[[image:1664503808294-336.png]]
19.2	832
	833
	834
51.16	835	* (% style="color:blue" %)Check the result, if the upload is successful, as shown below, open the serial port to view the data
19.2	836
50.2	837	[[image:1664503824081-592.png]] [[image:1664503831430-500.png]]
19.2	838
	839
	840
18.2	841	= 7. FAQ =
15.2	842
	843
18.2	844	== 7.1 How to change the LoRa Frequency Bands/Region? ==
14.1	845
	846
51.14	847	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	848
12.1	849
2.1	850
18.2	851	== 7.2 What is the pin mapping for the USB program cable? ==
2.1	852
7.1	853
18.2	854	[[image:1664499635206-262.png]]
7.1	855
	856
	857
18.2	858	(% border="2" style="background-color:#ffffcc; color:green; width:314px" %)
	859	\|(% style="width:118px" %)Pin\|(% style="width:67px" %)Color\|(% style="width:123px" %)USB Pin
	860	\|(% style="width:118px" %)A4,B4,A9,B9\|(% style="width:67px" %)Red\|(% style="width:123px" %)VCC
	861	\|(% style="width:118px" %)A7,B7\|(% style="width:67px" %)White\|(% style="width:123px" %)D- (N/A)
	862	\|(% style="width:118px" %)A6,B6\|(% style="width:67px" %)Green\|(% style="width:123px" %)D+(N/A)
	863	\|(% style="width:118px" %)A1,B1,A12,B12\|(% style="width:67px" %)Black\|(% style="width:123px" %)GND
	864	\|(% style="width:118px" %)A5\|(% style="width:67px" %)Purple\|(% style="width:123px" %)MTDC/GOIO13
	865	\|(% style="width:118px" %)B5\|(% style="width:67px" %)Blue\|(% style="width:123px" %)MTDC/GPIO12
	866	\|(% style="width:118px" %)A8\|(% style="width:67px" %)Yellow\|(% style="width:123px" %)MTMS/GPIO14
	867	\|(% style="width:118px" %)B8\|(% style="width:67px" %)Grey\|(% style="width:123px" %)MTDO/GPIO15
7.1	868
18.2	869	= 8. Order Info =
7.1	870
	871
15.6	872	Part Number: (% style="color:blue" %)TrackerD-XXX
8.1	873
15.6	874	(% style="color:blue" %)XXX(%%): The default frequency band
8.1	875
15.6	876	* (% style="color:red" %)EU433(%%): Default frequency band EU433
	877	* (% style="color:red" %)EU868(%%): Default frequency band EU868
	878	* (% style="color:red" %)IN865(%%): Default frequency band IN865
	879	* (% style="color:red" %)KR920(%%): Default frequency band KR920
	880	* (% style="color:red" %)AS923(%%): Default frequency band AS923
	881	* (% style="color:red" %)AU915(%%): Default frequency band AU915
	882	* (% style="color:red" %)US915(%%): Default frequency band US915
15.2	883
18.2	884	= 9. Packing Info =
	885
	886
8.1	887	Package Includes:
	888
50.3	889	* TrackerD LoRaWAN GPS/BLE Tracker x 1
	890	* USB recharge & program cable x 1
12.1	891
15.6	892	Dimensions and Weight:
12.1	893
50.3	894	* Device Size: 85 x 48 x 15 cm
	895	* Weight: 50g
15.6	896
18.2	897	= 10. Support =
	898
50.3	899
18.2	900	* 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.
50.3	901	* 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	902
	903	= 11. Reference =
	904
	905
12.1	906	* [[Firmware in Bin format>>https://www.dropbox.com/sh/733s8xlwahhqg1d/AABxDz80lBVX_to8zNuUQWFja?dl=0]]
	907	* [[Source Code>>https://github.com/dragino/TrackerD]]
	908	* [[Hardware Source>>https://www.dropbox.com/sh/orwoy6cecb89m4e/AAD37sRuUrvKsHgAJxuVTkB5a?dl=0]]

Wiki source code of TrackerD -LoRaWAN Tracker User Manual

Applications