Wiki source code of TrackerD -LoRaWAN Tracker User Manual

Version 58.1 by Edwin Chen on 2022/10/08 17:30

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

Wiki source code of TrackerD -LoRaWAN Tracker User Manual

Applications

Navigation