Wiki source code of TrackerD -LoRaWAN Tracker User Manual

Version 51.25 by Xiaoling on 2022/09/30 15:07

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
51.18	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.17	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
51.18	119
19.2	120	== 1.4 Applications ==
	121
	122
12.1	123	* Logistics and Supply Chain Management
	124	* Human tracking
	125
51.18	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
	189	(% style="color:blue" %)Positioning Mode(SMOD):
	190
51.9	191	* (% style="color:#037691" %)GPS ONLY(Factory Settings): (%%)only get GPS location info.
	192	* (% style="color:#037691" %)BLE ONLY: (%%)Only obtain iBeacon info via BLE. Design for Indoor tracking.
	193	* (% style="color:#037691" %)GPS/BLE Hybrid: (%%)Combination for Indoor and Outdoor tracking.
19.2	194
51.3	195	User can switch modes by [[changing SMOD>>\|\|anchor="H3.2.7SetPositioningMode"]].
19.2	196
	197
50.2	198
51.3	199	== 2.3 Uplink Payload ==
19.2	200
	201
50.2	202	=== 2.3.1 Uplink FPORT~=5, Device Status ===
19.2	203
	204
	205
51.3	206	=== 2.3.2 Uplink FPORT~= , Realtime GNSS Positioning ===
19.2	207
	208
50.2	209	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	210
50.2	211
51.24	212	(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:480px" %)
51.23	213	\|=(% scope="row" style="width: 50px;" %)(((
51.21	214	Size(bytes)
51.24	215	)))\|(% style="width:60px" %)4\|(% style="width:70px" %)4\|(% style="width:80px" %)2\|(% style="width:50px" %)1\|(% style="width:88px" %)(((
51.21	216	2(optional)
51.24	217	)))\|(% style="width:87px" %)(((
	218	2(optional)
19.2	219	)))
51.18	220	\|=(% style="width: 69px;" %)Value\|(% style="width:76px" %)[[Latitude>>\|\|anchor="HLocationinfo:"]]\|(% style="width:87px" %)[[Longitude>>\|\|anchor="HLocationinfo:"]]\|(% style="width:76px" %)(((
51.5	221	[[Alarm & BAT>>\|\|anchor="HAlarm26BAT:"]]
51.24	222	)))\|(% style="width:52px" %)[[FLAG>>\|\|anchor="HFLAG:"]]\|(% style="width:88px" %)[[Hum>>\|\|anchor="HHum:"]]\|(% style="width:87px" %)[[Tem>>\|\|anchor="HTem:"]]
19.2	223
50.2	224	[[image:1664501958445-288.png]]
19.2	225
50.2	226
51.24	227	==== (% style="color:blue" %)Alarm & BAT:(%%) ====
19.2	228
51.24	229	(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:250px" %)
	230	\|=(% scope="row" style="width: 50px;" %)Size(bit)\|(% style="width:50px" %)1 bit\|(% style="width:80px" %)1bit\|(% style="width:50px" %)14bits
51.22	231	\|=(% style="width: 72px;" %)Value\|(% style="width:67px" %)reserve\|(% style="width:118px" %)Alarm Indicate\|(% style="width:63px" %)[[BAT>>\|\|anchor="HBAT:"]]
19.2	232
50.2	233
51.24	234	==== (% style="color:blue" %)FLAG:(%%) ====
	235
	236	(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:250px" %)
	237	\|=(% scope="row" style="width: 50px;" %)Size(bit)\|(% style="width:50px" %)2bits\|(% style="width:50px" %)1bit\|(% style="width:100px" %)5 bits
51.22	238	\|=(% 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	239
51.11	240	Example: Payload: 0x02863D68 FAC29BAF 4B45 60 0202 011A
19.2	241
	242
51.24	243	==== (% style="color:blue" %)Location info:(%%) ====
19.2	244
51.11	245	* Latitude: 02863D68 ⇒ //if (0x//02863D68//& 0x80000000 = 0 )~:// //value = 02863D68 /1000000 = 42.351976//
	246	* Longitude: FAC29BAF ⇒ //if (0x//FAC29BAF// & 0x80000000 = 1 )~:// //value = (0x//FAC29BAF// – 0x 100000000)/1000000 =//-87.9094//57//
19.2	247
51.24	248
	249
51.9	250	(% style="color:red" %)Important note:
19.2	251
50.2	252	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	253
50.2	254	2. In firmware version v1.5, Roll & Pitch is disabled by default.
19.2	255
50.2	256	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	257
	258
50.2	259	[[image:1664502116362-706.png]]
19.2	260
	261
50.2	262
	263	4. While GPS can't get location info after timeout(FTIME Parameter), the latitude and longitude will be filled with all 0x00:
	264
	265	[[image:1664502166010-515.png]]
	266
	267
	268
51.24	269	==== (% style="color:blue" %)Alarm:(%%) ====
50.2	270
51.6	271	Example: 0x4B & 0x40 >> 6 = 0x01
19.2	272
	273
51.24	274	==== (% style="color:blue" %)BAT:(%%) ====
51.6	275
	276	Example: 0x0CDD & 0x3FFF ⇒ 3293 (mV).
	277
51.9	278	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	279
	280
50.4	281	* > 4.0v : 80% ~~ 100%
	282	* 3.85v ~~3.99v: 60% ~~ 80%
	283	* 3.70v ~~ 3.84v: 40% ~~ 60%
	284	* 3.40v ~~ 3.69v: 20% ~~ 40%
	285	* < 3.39v: 0~~20%
19.2	286
51.11	287
51.24	288
	289
	290	==== (% style="color:blue" %)LON:(%%) ====
	291
51.9	292
51.4	293	Enable/Disable LED activity for uplink
19.2	294
50.2	295	0x00: Disable LED indicator.
19.2	296
50.2	297	0x01: Enable LED indicator (Default Value)
19.2	298
	299
51.24	300	==== (% style="color:blue" %)Hum:(%%) ====
19.2	301
51.4	302	0202 = //if (0x0202 & 0x8000 = 0 ): value =// 0x0202 / 100 = +514 ⇒ 51.4 degree
19.2	303
	304
51.24	305	==== (% style="color:blue" %)Tem:(%%) ====
19.2	306
51.9	307	011A =if (0x011A & 0x8000 = 1 ): value =( 0x011A - 0x10000)/10(dec) ⇒ -//28.2 degree//
51.4	308
	309
	310
50.2	311	=== 2.3.3 Uplink FPORT~= , History GNSS Positioning ===
19.2	312
	313
50.2	314
	315	=== 2.3.4 BLE positioning Payload(Fport2) ===
	316
	317
19.2	318	Different MODE has different payload:
	319
	320	MODE=2
	321
51.25	322	(% border="1.5" cellspacing="3" style="background-color:#ffffcc; color:green; width:450px" %)
51.24	323	\|=(% scope="row" style="width: 50px;" %)(((
	324	Size(bytes)
	325	)))\|(% style="width:30px" %)16\|(% style="width:50px" %)4\|(% style="width:50px" %)4\|(% style="width:80px" %)2\|(% style="width:50px" %)4\|(% style="width:50px" %)2\|(% style="width:30px" %)1
	326	\|=(% style="width: 50px;" %)Value\|(% style="width:44px" %)[[UUID>>\|\|anchor="HLocationinfo:"]]\|(% style="width:61px" %)(((
51.8	327	iBeacon MAJOR
51.11	328	)))\|(% style="width:63px" %)(((
	329	iBeacon MINOR
50.2	330	)))\|(% style="width:71px" %)(((
51.8	331	iBeacon Measured Power
51.11	332	)))\|(% style="width:50px" %)(((
51.8	333	iBeacon RSSI
51.11	334	)))\|(% style="width:47px" %)(((
51.8	335	[[Alarm & BAT>>\|\|anchor="HAlarm26BAT:"]]
51.11	336	)))\|(% style="width:15px" %)[[FLAG>>\|\|anchor="HFLAG:"]]
19.2	337
50.2	338	[[image:1664502425687-834.png]]
19.2	339
	340
51.9	341	* (% style="color:#037691" %)BAT: (%%) Ex1: 0x4B45 & 0x3FFF ⇒ 3901 (mV).
	342	* (% style="color:#037691" %)MODE: (%%)Define the payload format.
	343	* (% style="color:#037691" %)UUID: (%%)The uuid from the strongest iBeacon.
	344	* (% style="color:#037691" %)MAJOR: (%%) The MAJOR from the strongest iBeacon.
	345	* (% style="color:#037691" %)MINOR: (%%)The MAJOR from the strongest iBeacon.
	346	* (% style="color:#037691" %)Measured Power: (%%) The Measured Power from the strongest iBeacon.
	347	* (% style="color:#037691" %)RSSI: (%%) The RSSI from the strongest iBeacon.
19.2	348
19.3	349	=== 2.3.5 Add Payload format in TTN V3 ===
	350
50.2	351
19.2	352	In TTN V3, use can add a custom payload so it shows friendly.
	353
51.9	354	In the page (% style="color:#037691" %)Applications ~-~-> Payload Formats ~-~-> Custom ~-~-> decoder
19.2	355
	356
50.2	357	[[image:1664502649601-895.png]]
	358
51.9	359
19.2	360	Add the decoder from this link:
	361
	362
	363	Save the change the uplink message will be parsed. As below:
	364
50.2	365	[[image:1664502676891-606.png]]
19.2	366
	367
	368
19.3	369	== 2.4 Integrate with Datacake ==
19.2	370
	371
	372	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.
	373
50.2	374	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	375
	376
50.2	377	[[image:1664502695771-538.png]]
19.2	378
50.2	379
	380
19.3	381	== 2.5 Integrate with Tago ==
19.2	382
	383
	384	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.
	385
	386	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]]
	387
	388
50.2	389	[[image:1664502715371-321.png]]
19.2	390
	391
	392
19.3	393	== 2.6 Alarm Mode ==
19.2	394
	395
51.11	396	User can push the (% style="color:red" %)RED button(%%) by more than 5 seconds to enter Alarm Mode.
19.2	397
	398
51.11	399	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	400
	401
	402	Two ways to exit alarm mode:
	403
	404	* Server send a downlink command to exit.
	405	* User fast press the RED button 10 times.
	406
51.11	407	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	408
	409
50.2	410
19.3	411	== 2.7 Sports Mode ~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-- ==
19.2	412
	413
	414
19.3	415	== 2.8 LED Status ==
19.2	416
	417
50.2	418	(% border="2" style="background-color:#ffffcc; color:green; width:636px" %)
	419	\|(% style="width:157px" %)Event\|(% style="width:271px" %)Action\|(% style="width:202px" %)AT+LON to control on/off
51.11	420	\|(% 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
	421	\|(% style="width:157px" %)Join request\|(% style="width:271px" %)(% style="color:green" %)Green (%%)led fast blink once (200ms)\|(% style="width:202px" %)Yes
	422	\|(% style="width:157px" %)Join Success\|(% style="width:271px" %)(% style="color:green" %)Green(%%) led on 5 second\|(% style="width:202px" %)N/A
	423	\|(% style="width:157px" %)Fixing Location\|(% style="width:271px" %)(% style="color:blue" %)BLUE (%%)blinks 200ms per second\|(% style="width:202px" %)Yes
	424	\|(% style="width:157px" %)Fixed and uplink\|(% style="width:271px" %)(% style="color:green" %)GREEN (%%)blinks twice (200ms per blink)\|(% style="width:202px" %)Yes
	425	\|(% style="width:157px" %)Fail Fix and uplink\|(% style="width:271px" %)(% style="color:red" %)RED (%%)blinks twice (200ms per blink)\|(% style="width:202px" %)Yes
	426	\|(% style="width:157px" %)Enter Alarm mode\|(% style="width:271px" %)(% style="color:red" %)RED (%%)on for 3 seconds\|(% style="width:202px" %)Yes
	427	\|(% style="width:157px" %)Uplink under Alarm\|(% style="width:271px" %)(% style="color:red" %)RED (%%)on for 1 second\|(% style="width:202px" %)Yes
	428	\|(% style="width:157px" %)Exit Alarm\|(% style="width:271px" %)(% style="color:blue" %)BLUE (%%)led on 5 second\|(% style="width:202px" %)Yes
	429	\|(% style="width:157px" %)Get Downlink\|(% style="width:271px" %)(% style="color:green" %)GREEN(%%) led on 1 second\|(% style="width:202px" %)Yes
	430	\|(% style="width:157px" %)Movement Detect\|(% style="width:271px" %)(% style="color:red" %)RED (%%)led on 500ms\|(% style="width:202px" %)N/A
19.2	431
19.3	432	== 2.9 Button Function ==
19.2	433
50.2	434
51.11	435	(% style="color:green" %)RESET button:
19.2	436
50.2	437	[[image:1664502835802-546.png]]
19.2	438
	439	Push this button will reboot the device. Device will exit alarm mode and re-join to LoRaWAN server.
	440
	441
51.11	442	(% style="color:red" %)RED button:
19.2	443
50.2	444	[[image:1664502854406-763.png]]
19.2	445
	446
50.2	447	(% border="2" style="background-color:#ffffcc; color:green; width:627px" %)
	448	\|(% style="width:135px" %)Function\|(% style="width:220px" %)Action\|(% style="width:265px" %)Description
51.11	449	\|(% 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"]]
	450	\|(% 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	451	\|(% 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	452
19.3	453	== 2.10 USB Port Function ==
19.2	454
50.2	455
19.2	456	The USB interface of TrackerD has below functions:
	457
	458	* Power on the device
	459	* Recharge the battery
51.11	460	* [[Configure Device>>\|\|anchor="H3.ConfigureTrackerDviaATcommandorLoRaWANdownlink"]]
	461	* [[Upgrade Firmware>>\|\|anchor="H5.UploadFirmware"]]
19.2	462
19.3	463	= 3. Configure TrackerD via AT command or LoRaWAN downlink =
19.2	464
	465
	466	User can configure TrackerD via AT Command or LoRaWAN Downlink.
	467
51.13	468	LoRaWAN Downlink instruction for different platforms: [[IoT LoRaWAN Server>>doc:Main.WebHome]]
19.2	469
	470
50.2	471
19.3	472	== 3.1 Access AT Command ==
19.2	473
	474
50.2	475	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	476
	477
50.2	478	[[image:1664502999401-486.png]]
	479
	480
51.11	481	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	482
	483
50.2	484	[[image:1664503022490-662.png]]
19.2	485
	486
	487
50.2	488	[[image:1664503035713-500.png]]
19.2	489
	490
	491
50.2	492	[[image:1664503047675-651.png]]
	493
	494
	495
19.3	496	== 3.2 Command Set ==
19.2	497
	498
19.3	499	=== 3.2.1 Set Transmit Interval ===
19.2	500
50.2	501
19.2	502	Set device uplink interval.
	503
51.13	504	* (% style="color:blue" %)AT Command:
19.2	505
51.13	506	(% style="color:#037691" %)AT+TDC=xxx
19.2	507
50.2	508	Example: AT+TDC=300000. Means set interval to 5 minutes(300 seconds)
19.2	509
	510
51.13	511	* (% style="color:blue" %)Downlink Payload (prefix 0x01):
19.2	512
51.13	513	(% style="color:#037691" %)0x01 00 01 2C (%%) ~/~/ Same as AT+TDC=300000
19.2	514
	515
50.2	516
19.3	517	=== 3.2.2 Set Alarm Packet transmission interval ===
19.2	518
50.2	519
19.2	520	Set alarm packet transmit interval
	521
51.13	522	* (% style="color:blue" %)AT Command:
19.2	523
51.13	524	(% style="color:#037691" %)AT+ATDC=xx.
19.2	525
51.2	526	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	527
	528
51.13	529	* (% style="color:blue" %)Downlink Payload (prefix 0xB1):
19.2	530
51.13	531	(% style="color:#037691" %)0xB1 00 00 3C (%%) ~/~/ Same as AT+ATDC=60000
19.2	532
	533
	534
50.2	535	=== 3.2.3 Set Sports Mode Packet transmission interval ===
	536
	537
19.2	538	Set sports packet transmit interval
	539
51.13	540	* (% style="color:blue" %)AT Command:
19.2	541
51.13	542	(% style="color:#037691" %)AT+MTDC=xx.
19.2	543
51.2	544	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	545
	546
51.13	547	* (% style="color:blue" %)Downlink Payload (prefix 0x03):
19.2	548
51.13	549	(% style="color:#037691" %)0x03 00 01 2C (%%) ~/~/ Same as AT+ MTDC=3000000
19.2	550
	551
	552
50.2	553	=== 3.2.4 Exit Alarm ===
19.2	554
50.2	555
19.2	556	Server send downlink command to exit Alarm mode
	557
51.13	558	* (% style="color:blue" %)AT Command: No AT Command
19.2	559
51.13	560	* (% style="color:blue" %)Downlink Payload (prefix 0x02):
19.2	561
51.13	562	(% style="color:#037691" %)0x02 01 (%%) ~/~/ Exit Alarm Mode
19.2	563
51.13	564
	565
50.2	566	=== 3.2.5 Disable/Enable LED flash ===
	567
	568
19.2	569	Disable/Enable LED for position, downlink and uplink
	570
51.13	571	* (% style="color:blue" %)AT Command:
19.2	572
51.13	573	(% style="color:#037691" %)AT+LON=xx. (Disable (0), Enable (1), default:1)
19.2	574
50.2	575	Example: AT+LON=0 ~-~-> Disable LED for position, downlink and uplink.
19.2	576
	577
51.13	578	* (% style="color:blue" %)Downlink Payload (prefix 0xAE):
19.2	579
51.13	580	(% style="color:#037691" %)0xAE 00 (%%) ~/~/ Same as AT+LON=0
19.2	581
	582
	583
50.2	584	=== 3.2.6 Disable/Enable movement detect (Debug Only) ===
19.2	585
	586
	587	User can use this feature to check and set thread hole of movement detect
	588
51.13	589	* (% style="color:blue" %)AT Command:
19.2	590
51.13	591	(% style="color:#037691" %)AT+INTWK=xx. (Disable (0), Enable (1), default:0)
19.2	592
51.2	593	Example: AT+ INTWK =1 ~-~-> Enable detect movement.
19.2	594
	595
51.13	596	* (% style="color:blue" %)Downlink Payload (prefix 0xAF):
19.2	597
51.13	598	(% style="color:#037691" %)0xAF 01 (%%) ~/~/ Same as AT+ INTWK =1
19.2	599
	600
	601
50.2	602	=== 3.2.7 Set Positioning Mode ===
19.2	603
50.2	604
19.2	605	SMOD define the how TrackerD scan and uplink date.
	606
50.2	607	GPS室外定位模式：设备默认模式，设备入网后会发送device当前模式下的信息，随后立即定位发送数据包（默认是3分钟定位，超过将发送无效数据），如果出现意外情况下，快速按键3下，将会发出报警消息（默认每分钟发送一次）。GPS还有一种logdata模式，在断网的情况下将数据存储下来，等到有网的时候，一次将数据以每10秒上报。
19.2	608
50.2	609	BLE室内定位模式：设备入网后会发送device当前模式下的信息，随后立即定位发送数据包（默认是5秒，超过将发送无效数据），如果出现意外情况下，快速按键3下，将会发出报警消息（默认每3分钟发送一次）。
19.2	610
50.2	611	GPS和BLE混动模式：设备入网后会发送device当前模式下的信息，随后立即判断是否在室内，如果是就进行BLE定位，不是就GPS定位。如果出现意外情况下，快速按键3下，将会发出报警消息（默认每分钟发送一次）。
19.2	612
50.2	613	运动模式：设备入网后会发送device当前模式下的信息，随后发送GPS定位数据，设备判断是否在运动，没有运动传感器没有检测到动作，立即进入静止状态（默认20分钟），如果产生运动，将每5分钟发送一次数据，再第五分钟后检测设备有误运动，无将切换到静止状态，有立即发送数据。
19.2	614
	615
	616
51.13	617	* (% style="color:blue" %)AT Command:
19.2	618
51.13	619	(% style="color:#037691" %)AT+SMOD=xx.
19.2	620
	621
50.2	622	Example:
19.2	623
50.2	624	AT+ SMOD =1,0 ~-~-> GPS+ BAT+ State+Tem&Hum
19.2	625
50.2	626	AT+ SMOD =1,1 ~-~-> GPS +BAT State
19.2	627
50.2	628	AT+ SMOD =2,3 ~-~-> (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State。
19.2	629
50.2	630
51.13	631	* (% style="color:blue" %)Downlink Payload (prefix 0xA5):
19.2	632
51.13	633	(% style="color:#037691" %)0xA5 01 00 (%%) ~/~/ Same as AT+ SMOD =1,0
19.2	634
	635
	636
50.2	637	=== 3.2.8 Set MAX GPS position time ===
	638
	639
19.2	640	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.
	641
	642
	643	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.
	644
	645
51.13	646	* (% style="color:blue" %)AT Command:
19.2	647
51.13	648	(% style="color:#037691" %)AT+FTIME=xx (%%) ~-~-> Set to use xx as max fix time.
19.2	649
50.2	650	Example: AT+FTIME=150
19.2	651
	652
51.13	653	* (% style="color:blue" %)Downlink Payload (prefix 0xAA):
19.2	654
51.13	655	(% style="color:#037691" %)0xAA 00 96 (%%) ~/~/ Set AT+FTIME=150
19.2	656
	657
	658
19.4	659	=== 3.3.9 Set PDOP value for GPS fix accuracy ===
19.2	660
	661
50.2	662	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	663
50.2	664
19.2	665	A GPS packet with lower PDOP has higher accuracy. PDOP default value is 2.0
	666
	667
51.13	668	* (% style="color:blue" %)AT Command:
19.2	669
51.13	670	(% style="color:#037691" %)AT+PDOP=2.5 (%%) ~-~-> Set PDOP to 2.5
19.2	671
	672
51.13	673	* (% style="color:blue" %)Downlink Payload (prefix 0xAD):
19.2	674
51.13	675	(% style="color:#037691" %)0xAD 00 0A (%%) ~/~/ Set AT+PDOP=1 (0x0A / 10 =1)
19.2	676
51.13	677	(% style="color:#037691" %)0xAD 00 19 (%%) ~/~/ Set AT+PDOP=2.5 (0x19 / 10 =2.5)
19.2	678
51.13	679	(% style="color:#037691" %)0xAD 00 46 (%%) ~/~/ Set AT+PDOP=7 (0x46 / 10 =7)
19.2	680
50.2	681
51.12	682
19.2	683	Disable/Enable the confirmation mode
	684
51.13	685	* (% style="color:blue" %)AT Command:
19.2	686
51.13	687	(% style="color:#037691" %)AT+CFM=xx.
19.2	688
	689
50.2	690	~ Example:
19.2	691
51.2	692	AT+ CFM=0 ~-~-> Disable confirmation
19.2	693
50.2	694	AT+ CFM=1 ~-~-> Enable confirmation
19.2	695
50.2	696
51.13	697	* (% style="color:blue" %)Downlink Payload (prefix 0x05):
19.2	698
51.13	699	(% style="color:#037691" %)0x05 01 (%%) ~/~/ Same as AT+ SMOD =1
19.2	700
	701
	702
19.4	703	= 4. Setting for Different Scenarios =
19.2	704
	705
	706
19.4	707	= 5. Upload Firmware =
19.2	708
19.4	709
	710	== 5.1 Firmware Change Log ==
	711
50.2	712
19.2	713	[[See this link>>url:https://github.com/dragino/TrackerD]]
	714
	715
50.2	716
19.4	717	== 5.2 How to upgrade firmware ==
19.2	718
	719
50.2	720	User can use the TrackerD's USB port to upgrade firmware into it. The hardware connection for upgrade firmware is as below:
19.2	721
	722
50.2	723	(% style="color:blue" %)Step1: (%%)Connect TrackerD and PC via USB cable shipped with TrackerD.
19.2	724
50.2	725
	726	(% style="color:blue" %)Step2: (%%) Install CH9102 driver in the PC.
	727
19.2	728	After installation of the driver and plug in TrackerD, user should be able to see com port in PC's device manager.
	729
	730
51.17	731	(% 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	732
	733
50.2	734	(% style="color:blue" %)Step4: (%%) Run Flash Download Tool and configure chip type to ESP32
19.2	735
	736
50.2	737	[[image:1664503563660-578.png]]
19.2	738
	739
50.2	740	[[image:1664503574618-659.png]]
19.2	741
50.2	742
	743	(% style="color:blue" %)Step5: (%%) Select the firmware file (.bin format), com port and proper SPI configure. Clink Start. Bin file location:
	744
19.2	745	[[https:~~/~~/www.dropbox.com/sh/733s8xlwahhqg1d/AABxDz80lBVX_to8zNuUQWFja?dl=0>>url:https://www.dropbox.com/sh/733s8xlwahhqg1d/AABxDz80lBVX_to8zNuUQWFja?dl=0]]
	746
	747
	748	Users need to use below files:
	749
	750	boot_app0.bin @0e000
	751
	752	ESP_LORA-eeprom-class.bin @ 0x10000
	753
	754
50.2	755	[[image:1664503593459-435.png]]
19.2	756
	757
	758
50.2	759	After upgrade finish, it will show finish as below:
19.2	760
50.2	761	[[image:1664503611848-385.png]]
19.2	762
	763
50.2	764
19.4	765	= 6. Developer Guide =
19.2	766
	767
19.4	768	== 6.1 Compile Source Code ==
	769
	770
	771	=== 6.1.1 Set up ARDUINO compile environment ===
	772
	773
50.2	774	* 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	775
51.15	776	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	777
	778
50.2	779	[[image:1664503635019-941.png]]
19.2	780
50.2	781
51.16	782	* (% style="color:#037691" %)Go to tools ~-~-> Boards ~-~-> Boards Manager,(%%) find the esp32 information and install it.
19.2	783
50.2	784	[[image:1664503715811-892.png]]
19.2	785
	786
	787
50.2	788	* Download the latest TrackerD from the dragino github: [[https:~~/~~/github.com/dragino/TrackerD>>url:https://github.com/dragino/TrackerD]]
19.2	789
50.2	790	Put the Library in the TrackerD directory into the libraries file in the Arduino directory:
19.2	791
	792
50.2	793	[[image:1664503752288-974.png]]
19.2	794
50.2	795
	796
19.4	797	== 6.2 Source Code ==
	798
	799
51.16	800	* (% style="color:blue" %)Open the example in the TrackerD file, please select the correct port in the IDE, as shown below:
19.2	801
50.2	802	[[image:1664503794261-827.png]]
19.2	803
	804
	805
51.16	806	* (% style="color:blue" %)Click to upload
19.2	807
50.2	808	[[image:1664503808294-336.png]]
19.2	809
	810
	811
51.16	812	* (% style="color:blue" %)Check the result, if the upload is successful, as shown below, open the serial port to view the data
19.2	813
50.2	814	[[image:1664503824081-592.png]] [[image:1664503831430-500.png]]
19.2	815
	816
	817
18.2	818	= 7. FAQ =
15.2	819
	820
18.2	821	== 7.1 How to change the LoRa Frequency Bands/Region? ==
14.1	822
	823
51.14	824	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	825
12.1	826
2.1	827
18.2	828	== 7.2 What is the pin mapping for the USB program cable? ==
2.1	829
7.1	830
18.2	831	[[image:1664499635206-262.png]]
7.1	832
	833
	834
18.2	835	(% border="2" style="background-color:#ffffcc; color:green; width:314px" %)
	836	\|(% style="width:118px" %)Pin\|(% style="width:67px" %)Color\|(% style="width:123px" %)USB Pin
	837	\|(% style="width:118px" %)A4,B4,A9,B9\|(% style="width:67px" %)Red\|(% style="width:123px" %)VCC
	838	\|(% style="width:118px" %)A7,B7\|(% style="width:67px" %)White\|(% style="width:123px" %)D- (N/A)
	839	\|(% style="width:118px" %)A6,B6\|(% style="width:67px" %)Green\|(% style="width:123px" %)D+(N/A)
	840	\|(% style="width:118px" %)A1,B1,A12,B12\|(% style="width:67px" %)Black\|(% style="width:123px" %)GND
	841	\|(% style="width:118px" %)A5\|(% style="width:67px" %)Purple\|(% style="width:123px" %)MTDC/GOIO13
	842	\|(% style="width:118px" %)B5\|(% style="width:67px" %)Blue\|(% style="width:123px" %)MTDC/GPIO12
	843	\|(% style="width:118px" %)A8\|(% style="width:67px" %)Yellow\|(% style="width:123px" %)MTMS/GPIO14
	844	\|(% style="width:118px" %)B8\|(% style="width:67px" %)Grey\|(% style="width:123px" %)MTDO/GPIO15
7.1	845
18.2	846	= 8. Order Info =
7.1	847
	848
15.6	849	Part Number: (% style="color:blue" %)TrackerD-XXX
8.1	850
15.6	851	(% style="color:blue" %)XXX(%%): The default frequency band
8.1	852
15.6	853	* (% style="color:red" %)EU433(%%): Default frequency band EU433
	854	* (% style="color:red" %)EU868(%%): Default frequency band EU868
	855	* (% style="color:red" %)IN865(%%): Default frequency band IN865
	856	* (% style="color:red" %)KR920(%%): Default frequency band KR920
	857	* (% style="color:red" %)AS923(%%): Default frequency band AS923
	858	* (% style="color:red" %)AU915(%%): Default frequency band AU915
	859	* (% style="color:red" %)US915(%%): Default frequency band US915
15.2	860
18.2	861	= 9. Packing Info =
	862
	863
8.1	864	Package Includes:
	865
50.3	866	* TrackerD LoRaWAN GPS/BLE Tracker x 1
	867	* USB recharge & program cable x 1
12.1	868
15.6	869	Dimensions and Weight:
12.1	870
50.3	871	* Device Size: 85 x 48 x 15 cm
	872	* Weight: 50g
15.6	873
18.2	874	= 10. Support =
	875
50.3	876
18.2	877	* 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	878	* 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	879
	880	= 11. Reference =
	881
	882
12.1	883	* [[Firmware in Bin format>>https://www.dropbox.com/sh/733s8xlwahhqg1d/AABxDz80lBVX_to8zNuUQWFja?dl=0]]
	884	* [[Source Code>>https://github.com/dragino/TrackerD]]
	885	* [[Hardware Source>>https://www.dropbox.com/sh/orwoy6cecb89m4e/AAD37sRuUrvKsHgAJxuVTkB5a?dl=0]]

Wiki source code of TrackerD -LoRaWAN Tracker User Manual

Applications