Wiki source code of TrackerD -LoRaWAN Tracker User Manual

Version 59.3 by Edwin Chen on 2022/10/08 18:10

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
59.2	248	=== 2.3.2 Uplink FPORT~=2, Realtime GNSS Positioning + Temperature & Humidity ===
55.1	249
	250
59.3	251	User can use AT+SMOD=1,0 to enable uploading on-board Temperature and humidity values, and the total payload will be 15 bytes, please note that 15 bytes won't work on DR0 on US915/AU915 frequency band.
55.1	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)
59.2	257	)))\|(% style="width:60px" %)4\|(% style="width:70px" %)4\|(% style="width:80px" %)2\|(% style="width:73px" %)1\|(% style="width:40px" %)(((
	258	2
51.24	259	)))\|(% style="width:87px" %)(((
59.2	260	2
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:"]]
59.2	264	)))\|(% style="width:73px" %)[[FLAG>>\|\|anchor="HFLAG:"]]\|(% style="width:40px" %)[[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" %)
59.3	278	\|=(% scope="row" style="width: 50px;" %)Size(bit)\|(% style="width:50px" %)2bits\|(% style="width:50px" %)1bit
	279	\|=(% style="width: 79px;" %)Value\|(% style="width:55px" %)[[MOD>>\|\|anchor="H3.2.7SetPositioningMode"]]\|(% style="width:47px" %)[[LON>>\|\|anchor="HLON:"]]
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
59.3	289
51.9	290	(% style="color:red" %)Important note:
19.2	291
50.2	292	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	293
59.3	294	2. In this mode, the total payload will be 15 bytes, while US915/AU915 DR0 accepts only 11 bytes payload. In this case, the payload on server will be ignore and shows as below:
19.2	295
	296
50.2	297	[[image:1664502116362-706.png]]
19.2	298
	299
59.3	300	3. While GPS can't get location info after timeout(FTIME Parameter), the latitude and longitude will be filled with all 0x00:
50.2	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	(((
59.3	316	The battery info shows the battery voltage, User can use the 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
59.3	325
51.24	326	==== (% style="color:blue" %)LON:(%%) ====
	327
51.4	328	Enable/Disable LED activity for uplink
19.2	329
51.27	330	(((
50.2	331	0x00: Disable LED indicator.
51.27	332	)))
19.2	333
51.27	334	(((
50.2	335	0x01: Enable LED indicator (Default Value)
51.27	336	)))
19.2	337
	338
51.24	339	==== (% style="color:blue" %)Hum:(%%) ====
19.2	340
51.4	341	0202 = //if (0x0202 & 0x8000 = 0 ): value =// 0x0202 / 100 = +514 ⇒ 51.4 degree
19.2	342
	343
51.24	344	==== (% style="color:blue" %)Tem:(%%) ====
19.2	345
51.9	346	011A =if (0x011A & 0x8000 = 1 ): value =( 0x011A - 0x10000)/10(dec) ⇒ -//28.2 degree//
51.4	347
	348
59.2	349	=== 2.3.3 Uplink FPORT~=3, Realtime GNSS Positioning (Default Mode) ===
51.4	350
59.2	351	The default uplink payload includes totally 11 bytes. The payload is the first 11 bytes of Uplink FPORT=2, real-time GNSS positioning, (remove the temp and humidity)
19.2	352
	353
59.2	354	(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:480px" %)
	355	\|=(% scope="row" style="width: 50px;" %)(((
	356	Size(bytes)
	357	)))\|(% style="width:60px" %)4\|(% style="width:70px" %)4\|(% style="width:80px" %)2\|(% style="width:73px" %)1
	358	\|=(% style="width: 69px;" %)Value\|(% style="width:76px" %)[[Latitude>>\|\|anchor="HLocationinfo:"]]\|(% style="width:87px" %)[[Longitude>>\|\|anchor="HLocationinfo:"]]\|(% style="width:76px" %)(((
	359	[[Alarm & BAT>>\|\|anchor="HAlarm26BAT:"]]
	360	)))\|(% style="width:73px" %)[[FLAG>>\|\|anchor="HFLAG:"]]
50.2	361
59.2	362
	363
59.3	364	=== 2.3.4 Uplink FPORT~=4, History GNSS Positioning ===
59.2	365
59.3	366	Set [[PNACKMD=1>>url:http://wiki.dragino.com/xwiki/bin/view/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LHT65N%20LoRaWAN%20Temperature%20%26%20Humidity%20Sensor%20Manual/#H4.13AutoSendNone-ACKmessages]], and TrackerD will wait for ACK for every uplink, when there is no LoRaWAN network, TrackerD will mark these records with non-ack messages and store the sensor data, and it will send all messages (10s interval) after the network recovery.
59.2	367
59.3	368	Note for this mode:
59.2	369
59.3	370	* a) TrackerD will do an ACK check for data records sending to make sure every data arrive server.
	371	* b) TrackerD will send data in CONFIRMED Mode when PNACKMD=1, but TrackerD won't re-transmit the packet if it doesn't get ACK, it will just mark it as a NONE-ACK message. In a future uplink, if TrackerD gets an ACK, TrackerD will consider there is a network connection and resend all NONE-ACK Messages.
50.2	372
59.3	373	The payload is 15 bytes, as below.
50.2	374
59.3	375
	376
	377	=== 2.3.5 BLE positioning Payload(Fport2) ===
	378
	379
51.28	380	Different MODE has different payload: (% style="color:blue" %)MODE=2
19.2	381
51.25	382	(% border="1.5" cellspacing="3" style="background-color:#ffffcc; color:green; width:450px" %)
51.26	383	\|=(% scope="row" style="width: 60px;" %)(((
51.24	384	Size(bytes)
51.26	385	)))\|(% 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	386	\|=(% style="width: 50px;" %)Value\|(% style="width:44px" %)[[UUID>>\|\|anchor="HLocationinfo:"]]\|(% style="width:61px" %)(((
51.8	387	iBeacon MAJOR
51.11	388	)))\|(% style="width:63px" %)(((
	389	iBeacon MINOR
50.2	390	)))\|(% style="width:71px" %)(((
51.8	391	iBeacon Measured Power
51.11	392	)))\|(% style="width:50px" %)(((
51.8	393	iBeacon RSSI
51.11	394	)))\|(% style="width:47px" %)(((
51.8	395	[[Alarm & BAT>>\|\|anchor="HAlarm26BAT:"]]
51.11	396	)))\|(% style="width:15px" %)[[FLAG>>\|\|anchor="HFLAG:"]]
19.2	397
50.2	398	[[image:1664502425687-834.png]]
19.2	399
	400
51.9	401	* (% style="color:#037691" %)BAT: (%%) Ex1: 0x4B45 & 0x3FFF ⇒ 3901 (mV).
	402	* (% style="color:#037691" %)MODE: (%%)Define the payload format.
	403	* (% style="color:#037691" %)UUID: (%%)The uuid from the strongest iBeacon.
	404	* (% style="color:#037691" %)MAJOR: (%%) The MAJOR from the strongest iBeacon.
	405	* (% style="color:#037691" %)MINOR: (%%)The MAJOR from the strongest iBeacon.
	406	* (% style="color:#037691" %)Measured Power: (%%) The Measured Power from the strongest iBeacon.
	407	* (% style="color:#037691" %)RSSI: (%%) The RSSI from the strongest iBeacon.
19.2	408
19.3	409	=== 2.3.5 Add Payload format in TTN V3 ===
	410
50.2	411
19.2	412	In TTN V3, use can add a custom payload so it shows friendly.
	413
51.9	414	In the page (% style="color:#037691" %)Applications ~-~-> Payload Formats ~-~-> Custom ~-~-> decoder
19.2	415
	416
50.2	417	[[image:1664502649601-895.png]]
	418
51.9	419
19.2	420	Add the decoder from this link:
	421
	422
	423	Save the change the uplink message will be parsed. As below:
	424
50.2	425	[[image:1664502676891-606.png]]
19.2	426
	427
	428
19.3	429	== 2.4 Integrate with Datacake ==
19.2	430
	431
51.27	432	(((
19.2	433	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	434	)))
19.2	435
51.27	436	(((
50.2	437	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	438	)))
19.2	439
	440
50.2	441	[[image:1664502695771-538.png]]
19.2	442
50.2	443
	444
19.3	445	== 2.5 Integrate with Tago ==
19.2	446
	447
51.27	448	(((
19.2	449	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	450	)))
19.2	451
51.27	452	(((
19.2	453	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	454	)))
19.2	455
	456
50.2	457	[[image:1664502715371-321.png]]
19.2	458
	459
	460
56.1	461	== 2.6 Datalog Feature ==
	462
	463
19.3	464	== 2.6 Alarm Mode ==
19.2	465
	466
51.27	467	(((
51.11	468	User can push the (% style="color:red" %)RED button(%%) by more than 5 seconds to enter Alarm Mode.
51.27	469	)))
19.2	470
	471
51.27	472	(((
51.11	473	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	474	)))
19.2	475
	476
51.27	477	(((
19.2	478	Two ways to exit alarm mode:
51.27	479	)))
19.2	480
	481	* Server send a downlink command to exit.
	482	* User fast press the RED button 10 times.
	483
51.27	484	(((
51.11	485	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	486	)))
19.2	487
	488
50.2	489
57.1	490	== 2.7 Transport Mode ==
19.2	491
	492
57.1	493	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	494
55.1	495
19.3	496	== 2.8 LED Status ==
19.2	497
	498
51.26	499	(% border="1.5" style="background-color:#ffffcc; color:green; width:500px" %)
51.27	500	\|=(% style="width: 150px;" %)Event\|=(% style="width: 200px;" %)Action\|=(% style="width: 150px;" %)AT+LON to control on/off
51.11	501	\|(% 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
	502	\|(% style="width:157px" %)Join request\|(% style="width:271px" %)(% style="color:green" %)Green (%%)led fast blink once (200ms)\|(% style="width:202px" %)Yes
	503	\|(% style="width:157px" %)Join Success\|(% style="width:271px" %)(% style="color:green" %)Green(%%) led on 5 second\|(% style="width:202px" %)N/A
	504	\|(% style="width:157px" %)Fixing Location\|(% style="width:271px" %)(% style="color:blue" %)BLUE (%%)blinks 200ms per second\|(% style="width:202px" %)Yes
	505	\|(% style="width:157px" %)Fixed and uplink\|(% style="width:271px" %)(% style="color:green" %)GREEN (%%)blinks twice (200ms per blink)\|(% style="width:202px" %)Yes
	506	\|(% style="width:157px" %)Fail Fix and uplink\|(% style="width:271px" %)(% style="color:red" %)RED (%%)blinks twice (200ms per blink)\|(% style="width:202px" %)Yes
	507	\|(% style="width:157px" %)Enter Alarm mode\|(% style="width:271px" %)(% style="color:red" %)RED (%%)on for 3 seconds\|(% style="width:202px" %)Yes
	508	\|(% style="width:157px" %)Uplink under Alarm\|(% style="width:271px" %)(% style="color:red" %)RED (%%)on for 1 second\|(% style="width:202px" %)Yes
	509	\|(% style="width:157px" %)Exit Alarm\|(% style="width:271px" %)(% style="color:blue" %)BLUE (%%)led on 5 second\|(% style="width:202px" %)Yes
	510	\|(% style="width:157px" %)Get Downlink\|(% style="width:271px" %)(% style="color:green" %)GREEN(%%) led on 1 second\|(% style="width:202px" %)Yes
	511	\|(% style="width:157px" %)Movement Detect\|(% style="width:271px" %)(% style="color:red" %)RED (%%)led on 500ms\|(% style="width:202px" %)N/A
19.2	512
19.3	513	== 2.9 Button Function ==
19.2	514
50.2	515
51.27	516	(% style="color:blue" %)RESET button:
19.2	517
50.2	518	[[image:1664502835802-546.png]]
19.2	519
	520	Push this button will reboot the device. Device will exit alarm mode and re-join to LoRaWAN server.
	521
	522
51.11	523	(% style="color:red" %)RED button:
19.2	524
50.2	525	[[image:1664502854406-763.png]]
19.2	526
	527
51.27	528	(% border="1.5" style="background-color:#ffffcc; color:green; width:520px" %)
	529	\|=(% style="width: 100px;" %)Function\|=(% style="width: 210px;" %)Action\|=(% style="width: 210px;" %)Description
51.11	530	\|(% 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"]]
	531	\|(% 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	532	\|(% 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	533
19.3	534	== 2.10 USB Port Function ==
19.2	535
50.2	536
19.2	537	The USB interface of TrackerD has below functions:
	538
	539	* Power on the device
	540	* Recharge the battery
51.11	541	* [[Configure Device>>\|\|anchor="H3.ConfigureTrackerDviaATcommandorLoRaWANdownlink"]]
	542	* [[Upgrade Firmware>>\|\|anchor="H5.UploadFirmware"]]
19.2	543
19.3	544	= 3. Configure TrackerD via AT command or LoRaWAN downlink =
19.2	545
	546
	547	User can configure TrackerD via AT Command or LoRaWAN Downlink.
	548
51.13	549	LoRaWAN Downlink instruction for different platforms: [[IoT LoRaWAN Server>>doc:Main.WebHome]]
19.2	550
	551
50.2	552
19.3	553	== 3.1 Access AT Command ==
19.2	554
	555
50.2	556	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	557
	558
50.2	559	[[image:1664502999401-486.png]]
	560
	561
51.11	562	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	563
	564
50.2	565	[[image:1664503022490-662.png]]
19.2	566
	567
	568
50.2	569	[[image:1664503035713-500.png]]
19.2	570
	571
	572
50.2	573	[[image:1664503047675-651.png]]
	574
	575
	576
19.3	577	== 3.2 Command Set ==
19.2	578
	579
19.3	580	=== 3.2.1 Set Transmit Interval ===
19.2	581
50.2	582
19.2	583	Set device uplink interval.
	584
51.13	585	* (% style="color:blue" %)AT Command:
19.2	586
51.13	587	(% style="color:#037691" %)AT+TDC=xxx
19.2	588
50.2	589	Example: AT+TDC=300000. Means set interval to 5 minutes(300 seconds)
19.2	590
	591
51.13	592	* (% style="color:blue" %)Downlink Payload (prefix 0x01):
19.2	593
51.13	594	(% style="color:#037691" %)0x01 00 01 2C (%%) ~/~/ Same as AT+TDC=300000
19.2	595
	596
50.2	597
19.3	598	=== 3.2.2 Set Alarm Packet transmission interval ===
19.2	599
50.2	600
19.2	601	Set alarm packet transmit interval
	602
51.13	603	* (% style="color:blue" %)AT Command:
19.2	604
51.13	605	(% style="color:#037691" %)AT+ATDC=xx.
19.2	606
51.2	607	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	608
	609
51.13	610	* (% style="color:blue" %)Downlink Payload (prefix 0xB1):
19.2	611
51.13	612	(% style="color:#037691" %)0xB1 00 00 3C (%%) ~/~/ Same as AT+ATDC=60000
19.2	613
	614
	615
57.1	616	=== 3.2.3 Set Transport Mode Packet transmission interval ===
50.2	617
	618
57.1	619	Set Transport Mode packet transmit interval
19.2	620
51.13	621	* (% style="color:blue" %)AT Command:
19.2	622
51.13	623	(% style="color:#037691" %)AT+MTDC=xx.
19.2	624
57.1	625	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	626
	627
51.13	628	* (% style="color:blue" %)Downlink Payload (prefix 0x03):
19.2	629
51.13	630	(% style="color:#037691" %)0x03 00 01 2C (%%) ~/~/ Same as AT+ MTDC=3000000
19.2	631
	632
	633
50.2	634	=== 3.2.4 Exit Alarm ===
19.2	635
50.2	636
19.2	637	Server send downlink command to exit Alarm mode
	638
51.13	639	* (% style="color:blue" %)AT Command: No AT Command
19.2	640
51.13	641	* (% style="color:blue" %)Downlink Payload (prefix 0x02):
19.2	642
51.13	643	(% style="color:#037691" %)0x02 01 (%%) ~/~/ Exit Alarm Mode
19.2	644
51.13	645
	646
50.2	647	=== 3.2.5 Disable/Enable LED flash ===
	648
	649
19.2	650	Disable/Enable LED for position, downlink and uplink
	651
51.13	652	* (% style="color:blue" %)AT Command:
19.2	653
51.13	654	(% style="color:#037691" %)AT+LON=xx. (Disable (0), Enable (1), default:1)
19.2	655
51.28	656	Example: AT+LON=0 ~-~-> Disable LED for position, downlink and uplink.
19.2	657
	658
51.13	659	* (% style="color:blue" %)Downlink Payload (prefix 0xAE):
19.2	660
51.13	661	(% style="color:#037691" %)0xAE 00 (%%) ~/~/ Same as AT+LON=0
19.2	662
	663
	664
59.1	665	=== 3.2.6 Disable/Enable Transport Mode ===
19.2	666
	667
59.1	668	Users can use this feature to enable/disable Transport Mode.
19.2	669
51.13	670	* (% style="color:blue" %)AT Command:
19.2	671
51.13	672	(% style="color:#037691" %)AT+INTWK=xx. (Disable (0), Enable (1), default:0)
19.2	673
59.1	674	Example: AT+ INTWK =1 ~-~-> Enable Transport Mode.
19.2	675
	676
51.13	677	* (% style="color:blue" %)Downlink Payload (prefix 0xAF):
19.2	678
51.13	679	(% style="color:#037691" %)0xAF 01 (%%) ~/~/ Same as AT+ INTWK =1
19.2	680
	681
	682
50.2	683	=== 3.2.7 Set Positioning Mode ===
19.2	684
50.2	685
55.1	686	SMOD define the how TrackerD scan and uplink data:
19.2	687
	688
51.13	689	* (% style="color:blue" %)AT Command:
19.2	690
51.13	691	(% style="color:#037691" %)AT+SMOD=xx.
19.2	692
	693
50.2	694	Example:
19.2	695
50.2	696	AT+ SMOD =1,0 ~-~-> GPS+ BAT+ State+Tem&Hum
19.2	697
50.2	698	AT+ SMOD =1,1 ~-~-> GPS +BAT State
19.2	699
50.2	700	AT+ SMOD =2,3 ~-~-> (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State。
19.2	701
50.2	702
51.13	703	* (% style="color:blue" %)Downlink Payload (prefix 0xA5):
19.2	704
51.13	705	(% style="color:#037691" %)0xA5 01 00 (%%) ~/~/ Same as AT+ SMOD =1,0
19.2	706
	707
	708
50.2	709	=== 3.2.8 Set MAX GPS position time ===
	710
	711
19.2	712	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.
	713
	714
	715	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.
	716
	717
51.13	718	* (% style="color:blue" %)AT Command:
19.2	719
51.13	720	(% style="color:#037691" %)AT+FTIME=xx (%%) ~-~-> Set to use xx as max fix time.
19.2	721
50.2	722	Example: AT+FTIME=150
19.2	723
	724
51.13	725	* (% style="color:blue" %)Downlink Payload (prefix 0xAA):
19.2	726
51.13	727	(% style="color:#037691" %)0xAA 00 96 (%%) ~/~/ Set AT+FTIME=150
19.2	728
	729
	730
19.4	731	=== 3.3.9 Set PDOP value for GPS fix accuracy ===
19.2	732
	733
50.2	734	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	735
50.2	736
19.2	737	A GPS packet with lower PDOP has higher accuracy. PDOP default value is 2.0
	738
	739
51.13	740	* (% style="color:blue" %)AT Command:
19.2	741
51.13	742	(% style="color:#037691" %)AT+PDOP=2.5 (%%) ~-~-> Set PDOP to 2.5
19.2	743
	744
51.13	745	* (% style="color:blue" %)Downlink Payload (prefix 0xAD):
19.2	746
51.13	747	(% style="color:#037691" %)0xAD 00 0A (%%) ~/~/ Set AT+PDOP=1 (0x0A / 10 =1)
19.2	748
51.13	749	(% style="color:#037691" %)0xAD 00 19 (%%) ~/~/ Set AT+PDOP=2.5 (0x19 / 10 =2.5)
19.2	750
51.13	751	(% style="color:#037691" %)0xAD 00 46 (%%) ~/~/ Set AT+PDOP=7 (0x46 / 10 =7)
19.2	752
50.2	753
51.12	754
19.2	755	Disable/Enable the confirmation mode
	756
51.13	757	* (% style="color:blue" %)AT Command:
19.2	758
51.13	759	(% style="color:#037691" %)AT+CFM=xx.
19.2	760
	761
50.2	762	~ Example:
19.2	763
51.2	764	AT+ CFM=0 ~-~-> Disable confirmation
19.2	765
50.2	766	AT+ CFM=1 ~-~-> Enable confirmation
19.2	767
50.2	768
51.13	769	* (% style="color:blue" %)Downlink Payload (prefix 0x05):
19.2	770
51.13	771	(% style="color:#037691" %)0x05 01 (%%) ~/~/ Same as AT+ SMOD =1
19.2	772
	773
	774
19.4	775	= 4. Setting for Different Scenarios =
19.2	776
	777
	778
19.4	779	= 5. Upload Firmware =
19.2	780
19.4	781
	782	== 5.1 Firmware Change Log ==
	783
50.2	784
19.2	785	[[See this link>>url:https://github.com/dragino/TrackerD]]
	786
	787
50.2	788
19.4	789	== 5.2 How to upgrade firmware ==
19.2	790
	791
50.2	792	User can use the TrackerD's USB port to upgrade firmware into it. The hardware connection for upgrade firmware is as below:
19.2	793
	794
50.2	795	(% style="color:blue" %)Step1: (%%)Connect TrackerD and PC via USB cable shipped with TrackerD.
19.2	796
50.2	797
	798	(% style="color:blue" %)Step2: (%%) Install CH9102 driver in the PC.
	799
19.2	800	After installation of the driver and plug in TrackerD, user should be able to see com port in PC's device manager.
	801
	802
51.28	803	(% 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	804
	805
50.2	806	(% style="color:blue" %)Step4: (%%) Run Flash Download Tool and configure chip type to ESP32
19.2	807
	808
50.2	809	[[image:1664503563660-578.png]]
19.2	810
	811
50.2	812	[[image:1664503574618-659.png]]
19.2	813
50.2	814
	815	(% style="color:blue" %)Step5: (%%) Select the firmware file (.bin format), com port and proper SPI configure. Clink Start. Bin file location:
	816
19.2	817	[[https:~~/~~/www.dropbox.com/sh/733s8xlwahhqg1d/AABxDz80lBVX_to8zNuUQWFja?dl=0>>url:https://www.dropbox.com/sh/733s8xlwahhqg1d/AABxDz80lBVX_to8zNuUQWFja?dl=0]]
	818
	819
	820	Users need to use below files:
	821
	822	boot_app0.bin @0e000
	823
	824	ESP_LORA-eeprom-class.bin @ 0x10000
	825
	826
50.2	827	[[image:1664503593459-435.png]]
19.2	828
	829
	830
50.2	831	After upgrade finish, it will show finish as below:
19.2	832
50.2	833	[[image:1664503611848-385.png]]
19.2	834
	835
50.2	836
19.4	837	= 6. Developer Guide =
19.2	838
	839
19.4	840	== 6.1 Compile Source Code ==
	841
	842
	843	=== 6.1.1 Set up ARDUINO compile environment ===
	844
	845
51.28	846	* 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	847
51.15	848	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	849
	850
50.2	851	[[image:1664503635019-941.png]]
19.2	852
50.2	853
51.28	854	* (% style="color:#037691" %)Go to tools ~-~-> Boards ~-~-> Boards Manager,(%%) find the esp32 information and install it.
19.2	855
50.2	856	[[image:1664503715811-892.png]]
19.2	857
	858
	859
51.28	860	* Download the latest TrackerD from the dragino github: [[https:~~/~~/github.com/dragino/TrackerD>>url:https://github.com/dragino/TrackerD]]
19.2	861
50.2	862	Put the Library in the TrackerD directory into the libraries file in the Arduino directory:
19.2	863
	864
50.2	865	[[image:1664503752288-974.png]]
19.2	866
50.2	867
	868
19.4	869	== 6.2 Source Code ==
	870
	871
51.16	872	* (% style="color:blue" %)Open the example in the TrackerD file, please select the correct port in the IDE, as shown below:
19.2	873
50.2	874	[[image:1664503794261-827.png]]
19.2	875
	876
	877
51.16	878	* (% style="color:blue" %)Click to upload
19.2	879
50.2	880	[[image:1664503808294-336.png]]
19.2	881
	882
	883
51.16	884	* (% style="color:blue" %)Check the result, if the upload is successful, as shown below, open the serial port to view the data
19.2	885
50.2	886	[[image:1664503824081-592.png]] [[image:1664503831430-500.png]]
19.2	887
	888
	889
18.2	890	= 7. FAQ =
15.2	891
	892
18.2	893	== 7.1 How to change the LoRa Frequency Bands/Region? ==
14.1	894
	895
51.14	896	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	897
12.1	898
2.1	899
18.2	900	== 7.2 What is the pin mapping for the USB program cable? ==
2.1	901
7.1	902
18.2	903	[[image:1664499635206-262.png]]
7.1	904
	905
	906
51.28	907	(% border="1.5" cellspacing="3" style="background-color:#ffffcc; color:green; width:314px" %)
51.27	908	\|=(% style="width: 118px;" %)Pin\|=(% style="width: 67px;" %)Color\|=(% style="width: 123px;" %)USB Pin
18.2	909	\|(% style="width:118px" %)A4,B4,A9,B9\|(% style="width:67px" %)Red\|(% style="width:123px" %)VCC
	910	\|(% style="width:118px" %)A7,B7\|(% style="width:67px" %)White\|(% style="width:123px" %)D- (N/A)
	911	\|(% style="width:118px" %)A6,B6\|(% style="width:67px" %)Green\|(% style="width:123px" %)D+(N/A)
	912	\|(% style="width:118px" %)A1,B1,A12,B12\|(% style="width:67px" %)Black\|(% style="width:123px" %)GND
	913	\|(% style="width:118px" %)A5\|(% style="width:67px" %)Purple\|(% style="width:123px" %)MTDC/GOIO13
	914	\|(% style="width:118px" %)B5\|(% style="width:67px" %)Blue\|(% style="width:123px" %)MTDC/GPIO12
	915	\|(% style="width:118px" %)A8\|(% style="width:67px" %)Yellow\|(% style="width:123px" %)MTMS/GPIO14
	916	\|(% style="width:118px" %)B8\|(% style="width:67px" %)Grey\|(% style="width:123px" %)MTDO/GPIO15
7.1	917
18.2	918	= 8. Order Info =
7.1	919
	920
15.6	921	Part Number: (% style="color:blue" %)TrackerD-XXX
8.1	922
15.6	923	(% style="color:blue" %)XXX(%%): The default frequency band
8.1	924
15.6	925	* (% style="color:red" %)EU433(%%): Default frequency band EU433
	926	* (% style="color:red" %)EU868(%%): Default frequency band EU868
	927	* (% style="color:red" %)IN865(%%): Default frequency band IN865
	928	* (% style="color:red" %)KR920(%%): Default frequency band KR920
	929	* (% style="color:red" %)AS923(%%): Default frequency band AS923
	930	* (% style="color:red" %)AU915(%%): Default frequency band AU915
	931	* (% style="color:red" %)US915(%%): Default frequency band US915
15.2	932
18.2	933	= 9. Packing Info =
	934
	935
51.30	936	(% style="color:#037691" %)Package Includes:
8.1	937
50.3	938	* TrackerD LoRaWAN GPS/BLE Tracker x 1
	939	* USB recharge & program cable x 1
12.1	940
51.30	941	(% style="color:#037691" %)Dimensions and Weight:
12.1	942
50.3	943	* Device Size: 85 x 48 x 15 cm
	944	* Weight: 50g
15.6	945
18.2	946	= 10. Support =
	947
50.3	948
18.2	949	* 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	950	* 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	951
	952	= 11. Reference =
	953
	954
12.1	955	* [[Firmware in Bin format>>https://www.dropbox.com/sh/733s8xlwahhqg1d/AABxDz80lBVX_to8zNuUQWFja?dl=0]]
	956	* [[Source Code>>https://github.com/dragino/TrackerD]]
	957	* [[Hardware Source>>https://www.dropbox.com/sh/orwoy6cecb89m4e/AAD37sRuUrvKsHgAJxuVTkB5a?dl=0]]
51.28	958
	959

Wiki source code of TrackerD -LoRaWAN Tracker User Manual

Applications