Wiki source code of TrackerD -LoRaWAN Tracker User Manual

Version 158.1 by Bei Jinggeng on 2022/11/28 11:05

version	line-number	content
51.2	1	(% style="text-align:center" %)
146.1	2	[[image:1664505654417-133.png\|\|_mstalt="293696"]]
51.2	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
50.2	17	== 1.1 What is TrackerD ==
15.2	18
50.2	19
15.3	20	(((
	21	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.
	22	)))
7.2	23
15.3	24	(((
19.2	25	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	26
51.18	27	(((
8.1	28	TrackerD is program friendly. Developers can use Arduino IDE to customize the software of TrackerD to fit their IoT solution.
51.18	29	)))
8.1	30
51.18	31	(((
19.2	32	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	33	)))
8.1	34
15.3	35	(((
	36	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.
	37	)))
8.1	38
146.1	39	[[image:1664499921684-770.png\|\|_mstalt="298194"]]
8.1	40
15.4	41
19.2	42	(% style="color:red" %)Note: LoRaWAN server can be a general LoRaWAN server other than TTN.
8.1	43
15.2	44
19.2	45	== 1.2 Specifications ==
12.1	46
15.2	47
19.2	48	(% style="color:blue" %)Micro Controller:
15.2	49
19.2	50	* Espressif ESP32 PICO D4
	51	* MCU: ESP32 PICO D4
	52	* Bluetooth: Bluetooth V4.2 BR/EDR and Bluetooth LE
	53	* WiFi : 802.11 b/g/n (802.11n up to 150 Mbps)
	54	* Integrated SPI flash : 4 MB
	55	* RAM: 448 KB
	56	* EEPROM: 520 KB
	57	* Clock Speed: 32Mhz
	58
	59	(% style="color:blue" %)Common DC Characteristics:
	60
	61	* Supply Voltage: 5V via USB port or Internal li-on battery
	62	* Operating Temperature: -40 ~~ 60°C
	63
	64	(% style="color:blue" %)LoRa Spec:
	65
	66	* Frequency Range,
	67	** Band 1 (HF): 862 ~~ 1020 Mhz
	68	* 168 dB maximum link budget.
	69	* +20 dBm - 100 mW constant RF output vs.
	70	* +14 dBm high efficiency PA.
	71	* Programmable bit rate up to 300 kbps.
	72	* High sensitivity: down to -148 dBm.
	73	* Bullet-proof front end: IIP3 = -12.5 dBm.
	74	* Excellent blocking immunity.
	75	* Low RX current of 10.3 mA, 200 nA register retention.
	76	* Fully integrated synthesizer with a resolution of 61 Hz.
	77	* FSK, GFSK, MSK, GMSK, LoRaTM and OOK modulation.
	78	* Built-in bit synchronizer for clock recovery.
	79	* Preamble detection.
	80	* 127 dB Dynamic Range RSSI.
	81	* Automatic RF Sense and CAD with ultra-fast AFC.
	82	* Packet engine up to 256 bytes with CRC.
	83	* LoRaWAN 1.0.3 Specification
	84
	85	(% style="color:blue" %)Battery:
	86
	87	* 1000mA Li-on Battery power (for model TrackerD)
	88
	89	(% style="color:blue" %)Power Consumption
	90
	91	* Sleeping Mode: 200uA
	92	* LoRa Transmit Mode: 125mA @ 20dBm 44mA @ 14dBm
	93	* Tracking: max: 38mA
	94
155.3	95
	96
19.2	97	== 1.3 Features ==
	98
	99
	100	* LoRaWAN 1.0.3 Class A
	101	* ESP32 PICO D4
	102	* SX1276/78 Wireless Chip
51.31	103	* Arduino IDE Compatible
19.2	104	* Open source hardware / software
	105	* Regular/ Real-time GPS,BLE,WIFI tracking
	106	* Built-in3 axis accelerometer (LIS3DH)
	107	* Humidity / temperature sensor : GXCAS Technology GXHT3X
	108	* Motion sensing capability
	109	* Power Monitoring
	110	* Charging circuit via USB port
	111	* 1000mA Li-on Battery power
	112	* Tri-color LED, Alarm button
	113	* Datalog
	114
155.3	115
	116
19.2	117	== 1.4 Applications ==
	118
	119
12.1	120	* Logistics and Supply Chain Management
	121	* Human tracking
	122
155.3	123
	124
105.2	125	= 2. Use TrackerD =
	126
19.3	127	== 2.1 How it works? ==
19.2	128
19.3	129
19.2	130	TrackerD is configured as LoRaWAN OTAA Class A GPS tracker by default. It has OTAA keys to join LoRaWAN network. To connect a LoRaWAN network, user need to input the OTAA keys in the LoRaWAN IoT server and push reset button of TrackerD (next to USB port). TrackerD will wake up and auto join the network via OTAA.
	131
	132
19.3	133	== 2.2 Quick guide to connect to LoRaWAN server ==
19.2	134
	135
50.2	136	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	137
	138
146.1	139	[[image:1664501652064-326.png\|\|_mstalt="293306"]]
19.2	140
50.2	141
	142
19.2	143	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:
	144
	145
50.2	146	(% style="color:blue" %)Step 1:(%%) Create a device in TTN V3 with the OTAA keys from TrackerD.
	147
19.2	148	Each TrackerD is shipped with a sticker with the default device EUI as below:
	149
51.3	150
146.1	151	[[image:1664501677253-891.png\|\|_mstalt="296569"]]
19.2	152
	153
	154	Input these keys to their LoRaWAN Server portal. Below is TTN V3 screen shot:
	155
	156
50.2	157	__Add APP EUI in the application:__
19.2	158
	159
146.1	160	[[image:1664501711466-918.png\|\|_mstalt="295828"]]
19.2	161
	162
	163
146.1	164	[[image:1664501721248-725.png\|\|_mstalt="294450"]]
19.2	165
	166
146.1	167	[[image:1664501734705-405.png\|\|_mstalt="293306"]]
19.2	168
	169
	170
50.2	171	__Add APP KEY and DEV EUI:__
19.2	172
	173
146.1	174	[[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LDS02%20-%20LoRaWAN%20Door%20Sensor%20User%20Manual/WebHome/1654671889112-678.png?rev=1.1\|\|_mstalt="298233" alt="1654671889112-678.png"]]
19.2	175
	176
	177
125.1	178	(% style="color:blue" %)Step 2:(%%) Push this button will activate this device.
19.2	179
146.1	180	(% id="cke_bm_7709S" style="display:none" %) [[image:1664502835802-546.png\|\|_mstalt="295061"]]
50.2	181
146.1	182	[[image:1664502835802-546.png\|\|_mstalt="295061"]]
124.1	183
	184
50.2	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
66.3	188	== 2.3 Positioning Mode(SMOD) ==
50.2	189
66.3	190
55.1	191	Users can set TrackerD to different Positioning Mode for different applications. Below mod are supported.
19.2	192
87.1	193	* (% style="color:#037691" %)GPS ONLY(Factory Settings): (%%)Only get and uplink GPS location info.
	194	* (% style="color:#037691" %)BLE or WiFi ONLY: (%%) Only obtain iBeacon info via BLE and uplink or obtain wifi ssid info via WiFi and uplink. Design for Indoor tracking.
88.1	195	* (% 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	196
55.1	197	Users can switch modes by [[changing SMOD>>\|\|anchor="H3.2.7SetPositioningMode"]].
19.2	198
50.2	199
66.3	200	== 2.4 Uplink Payload ==
19.2	201
66.3	202	=== 2.4.1 Uplink FPORT~=5, Device Status ===
66.2	203
66.3	204
74.1	205	Uplink the device configures with FPORT=5. Once TrackerD Joined the network, it will uplink this message to the server. After the first uplink, TrackerD will uplink Device Status every 12 hours.
19.2	206
76.1	207	Use can also get the Device Status uplink through the downlink command: Downlink: 0x2301
19.2	208
76.1	209
84.8	210	(% border="1.5" style="background-color:#ffffcc; color:green; width:440px" %)
84.9	211	\|=(% style="width: 60px;" %)Size(bytes)\|=(% style="width: 70px;" %)1\|=(% style="width: 70px;" %)2\|=(% style="width: 70px;" %)1\|=(% style="width: 50px;" %)1\|=(% style="width: 30px;" %)2\|=(% style="width: 40px;" %)2\|=(% style="width: 40px;" %)1
66.2	212	\|=(% style="width: 108px;" %)Value\|(% style="width:82px" %)Sensor Model\|(% style="width:83px" %)Firmware Version\|(% style="width:94px" %)Frequency Band\|(% style="width:84px" %)Sub-band\|(% style="width:44px" %)BAT\|(% style="width:63px" %)SMOD\|(% style="width:60px" %)Status
19.2	213
146.1	214	[[image:1665301570342-765.png\|\|_mstalt="294580"]]
66.2	215
	216
74.2	217	(% style="color:#037691" %)Example of Device Status:(%%) 13014001FF0FA24002
19.2	218
74.2	219	(% style="color:#037691" %)Sensor Model: (%%) For TrackerD,this value is 0x13
19.2	220
74.2	221	(% style="color:#037691" %)Firmware Version: (%%) 0x0140,Means:v1.4.0 version
50.2	222
74.2	223	(% style="color:#037691" %)Frequency Band:
55.1	224
	225	*0x01: EU868
	226
	227	*0x02: US915
	228
	229	*0x03: IN865
	230
	231	*0x04: AU915
	232
	233	*0x05: KZ865
	234
	235	*0x06: RU864
	236
	237	*0x07: AS923
	238
	239	*0x08: AS923-1
	240
	241	*0x09: AS923-2
	242
	243	*0x0a: AS923-3
	244
74.2	245	Sub- Band:value 0x00~~0x08(only forAU915,US915,Others are 0xFF)
55.1	246
74.2	247	(% style="color:#037691" %)BAT:(%%) shows the battery voltage for TrackerD.
55.1	248
	249
74.2	250	(% style="color:#037691" %)Ex1:(%%) 0x0FA2 = 4002mV
	251
55.1	252	Use can also get the Device Status uplink through the downlink command:
	253
	254
75.1	255	(% style="color:#037691" %)SMOD Field (total 1 byte)(%%)：0x40
74.2	256
84.11	257	(% border="1.5" style="background-color:#ffffcc; color:green; width:270px" %)
84.10	258	\|=(% scope="row" style="width: 60px;" %)Size(bit)\|(% style="width:50px" %)2bits\|(% style="width:80px" %)2bit\|(% style="width:80px" %)4bit
84.9	259	\|=(% style="width: 75px;" %)Value\|(% style="width:64px" %)SMOD\|(% style="width:104px" %)GPS_Settings\|(% style="width:103px" %)BLE_Settings
74.2	260
75.1	261	(% style="color:blue" %) SMOD：
74.2	262
75.1	263	(% style="color:red" %) 1 : (%%) GPS ONLY
74.2	264
75.1	265	(% style="color:red" %) 2 : (%%) BLE ONLY
74.2	266
75.1	267	(% style="color:red" %) 3 : (%%) GPS/BLE Hybrid
74.2	268
	269
75.1	270	(% style="color:blue" %) GPS_MOD: Define how to send GPS payload
74.2	271
75.1	272	(% style="color:red" %) 0 : (%%) Enable uploading on-board Temperature and humidity values
74.2	273
75.1	274	(% style="color:red" %) 1 : (%%) Disable uploading on-board Temperature and humidity values
74.2	275
	276
75.1	277	(% style="color:blue" %) BLE_Settings:
74.2	278
75.1	279	(% style="color:red" %) 1: (%%) BLE Positioning with Strongest iBeacon
74.2	280
146.1	281	(% _mstmutation="1" style="color:red" %) 2： (%%)WiFi Positioning with Strongest WiFi SSID(% _mstmutation="1" style="color:blue" %)(V1.4.1 Version support this function later)(%%)
74.2	282
88.1	283
75.1	284	(% style="color:#037691" %)Status Field (total 1 byte)(%%): 0x02
74.2	285
84.11	286	(% border="1.5" style="background-color:#ffffcc; color:green; width:260px" %)
	287	\|=(% scope="row" style="width: 50px;" %)Size(bit)\|(% style="width:50px" %)5 Bits\|(% style="width:60px" %)1 Bit\|(% style="width:20px" %)1 Bit\|(% style="width:80px" %)1 Bit
84.9	288	\|=(% style="width: 77px;" %)Value\|(% style="width:70px" %)Reserve\|(% style="width:92px" %)[[PNACKMD>>\|\|anchor="H2.4.4A0UplinkFPORT3D42CHistoryGNSSPositioning"]]\|(% style="width:48px" %)[[LON>>\|\|anchor="H3.2.5Disable2FEnableLEDflash"]]\|(% style="width:126px" %)[[Transport Mode>>\|\|anchor="H2.9TransportMode"]]
74.2	289
155.3	290
155.4	291
66.3	292	=== 2.4.2 Uplink FPORT~=2, Realtime GNSS Positioning + Temperature & Humidity ===
55.1	293
	294
77.1	295	Users can use AT+SMOD=1,0,0 to enable uploading on-board Temperature and humidity values, and the total payload will be 15 bytes,
55.1	296
	297
84.13	298	(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:320px" %)
	299	\|=(% scope="row" style="width: 60px;" %)(((
84.19	300	Size(bytes)
	301	)))\|(% style="width:50px" %)4\|(% style="width:50px" %)4\|(% style="width:70px" %)2\|(% style="width:30px" %)1\|(% style="width:30px" %)(((
	302	2
	303	)))\|(% style="width:30px" %)(((
	304	2
	305	)))
51.18	306	\|=(% style="width: 69px;" %)Value\|(% style="width:76px" %)[[Latitude>>\|\|anchor="HLocationinfo:"]]\|(% style="width:87px" %)[[Longitude>>\|\|anchor="HLocationinfo:"]]\|(% style="width:76px" %)(((
51.5	307	[[Alarm & BAT>>\|\|anchor="HAlarm26BAT:"]]
59.2	308	)))\|(% style="width:73px" %)[[FLAG>>\|\|anchor="HFLAG:"]]\|(% style="width:40px" %)[[Hum>>\|\|anchor="HHum:"]]\|(% style="width:87px" %)[[Tem>>\|\|anchor="HTem:"]]
19.2	309
146.1	310	[[image:1665301636888-168.png\|\|_mstalt="298012"]]
19.2	311
50.2	312
51.24	313	==== (% style="color:blue" %)Alarm & BAT:(%%) ====
19.2	314
51.24	315	(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:250px" %)
	316	\|=(% scope="row" style="width: 50px;" %)Size(bit)\|(% style="width:50px" %)1 bit\|(% style="width:80px" %)1bit\|(% style="width:50px" %)14bits
51.22	317	\|=(% style="width: 72px;" %)Value\|(% style="width:67px" %)reserve\|(% style="width:118px" %)Alarm Indicate\|(% style="width:63px" %)[[BAT>>\|\|anchor="HBAT:"]]
19.2	318
51.24	319	==== (% style="color:blue" %)FLAG:(%%) ====
	320
84.12	321	(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:120px" %)
	322	\|=(% scope="row" style="width: 50px;" %)Size(bit)\|(% style="width:30px" %)2bits\|(% style="width:30px" %)1bit
59.3	323	\|=(% style="width: 79px;" %)Value\|(% style="width:55px" %)[[MOD>>\|\|anchor="H3.2.7SetPositioningMode"]]\|(% style="width:47px" %)[[LON>>\|\|anchor="HLON:"]]
19.2	324
51.11	325	Example: Payload: 0x02863D68 FAC29BAF 4B45 60 0202 011A
19.2	326
	327
51.24	328	==== (% style="color:blue" %)Location info:(%%) ====
19.2	329
51.11	330	* Latitude: 02863D68 ⇒ //if (0x//02863D68//& 0x80000000 = 0 )~:// //value = 02863D68 /1000000 = 42.351976//
	331	* Longitude: FAC29BAF ⇒ //if (0x//FAC29BAF// & 0x80000000 = 1 )~:// //value = (0x//FAC29BAF// – 0x 100000000)/1000000 =//-87.9094//57//
19.2	332
51.9	333	(% style="color:red" %)Important note:
19.2	334
50.2	335	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	336
59.3	337	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	338
	339
146.1	340	[[image:1664502116362-706.png\|\|_mstalt="293306"]]
19.2	341
	342
59.3	343	3. While GPS can't get location info after timeout(FTIME Parameter), the latitude and longitude will be filled with all 0x00:
50.2	344
146.1	345	[[image:1664502166010-515.png\|\|_mstalt="291395"]]
50.2	346
	347
	348
51.24	349	==== (% style="color:blue" %)Alarm:(%%) ====
50.2	350
74.9	351	Example: 0x4B & 0x40 >> 6 = 0x01
19.2	352
	353
51.24	354	==== (% style="color:blue" %)BAT:(%%) ====
51.6	355
74.9	356	Example: 0x4B45 & 0x3FFF ⇒ 2885 (mV).
51.6	357
51.27	358	(((
59.3	359	The battery info shows the battery voltage, User can use the below mapping to indicate the battery in percentage: \
51.27	360	)))
51.6	361
50.4	362	* > 4.0v : 80% ~~ 100%
	363	* 3.85v ~~3.99v: 60% ~~ 80%
	364	* 3.70v ~~ 3.84v: 40% ~~ 60%
	365	* 3.40v ~~ 3.69v: 20% ~~ 40%
	366	* < 3.39v: 0~~20%
19.2	367
155.3	368
	369
74.3	370	==== (% style="color:blue" %)MOD:(%%) ====
	371
79.1	372	Example: (0x60>>6) & 0x3f =1
74.10	373
74.7	374	Set the format of GPS data uplink link：
74.3	375
74.7	376	(% style="color:#037691" %)0x00: (%%) Enable uploading on-board Temperature and humidity values
74.9	377	(% style="color:#037691" %)0x01: (%%) Disable uploading on-board Temperature and humidity values
74.3	378
	379
74.7	380	Set the format of BLE data uplink link：
74.3	381
74.7	382	(% style="color:#037691" %)0x01: (%%) BLE Positioning with Strongest iBeacon
	383
	384
74.10	385	==== (% style="color:blue" %)LON:(%%) ====
74.9	386
74.10	387	Example: (0x60>>5) & 0x01=1.
74.9	388
51.4	389	Enable/Disable LED activity for uplink
19.2	390
51.27	391	(((
74.7	392	(% style="color:#037691" %)0x00: (%%) Disable LED indicator.
51.27	393	)))
19.2	394
51.27	395	(((
74.7	396	(% style="color:#037691" %)0x01: (%%) Enable LED indicator (Default Value)
51.27	397	)))
19.2	398
	399
51.24	400	==== (% style="color:blue" %)Hum:(%%) ====
19.2	401
51.4	402	0202 = //if (0x0202 & 0x8000 = 0 ): value =// 0x0202 / 100 = +514 ⇒ 51.4 degree
19.2	403
	404
51.24	405	==== (% style="color:blue" %)Tem:(%%) ====
19.2	406
51.9	407	011A =if (0x011A & 0x8000 = 1 ): value =( 0x011A - 0x10000)/10(dec) ⇒ -//28.2 degree//
51.4	408
	409
66.3	410	=== 2.4.3 Uplink FPORT~=3, Realtime GNSS Positioning (Default Mode) ===
51.4	411
66.2	412
78.1	413	The default uplink payload includes total 11 bytes (AT+SMOD=1,1,0). The payload is the first 11 bytes of Uplink FPORT=2, real-time GNSS positioning, (remove the temp and humidity)
19.2	414
	415
84.14	416	(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:300px" %)
84.19	417	\|=(% scope="row" style="width: 60px;" %)(((
	418	Size(bytes)
	419	)))\|(% style="width:60px" %)4\|(% style="width:60px" %)4\|(% style="width:60px" %)2\|(% style="width:50px" %)1
59.2	420	\|=(% style="width: 69px;" %)Value\|(% style="width:76px" %)[[Latitude>>\|\|anchor="HLocationinfo:"]]\|(% style="width:87px" %)[[Longitude>>\|\|anchor="HLocationinfo:"]]\|(% style="width:76px" %)(((
	421	[[Alarm & BAT>>\|\|anchor="HAlarm26BAT:"]]
	422	)))\|(% style="width:73px" %)[[FLAG>>\|\|anchor="HFLAG:"]]
50.2	423
66.2	424	(% class="wikigeneratedid" %)
146.1	425	[[image:1665301687277-443.png\|\|_mstalt="296140"]]
66.2	426
	427
66.3	428	=== 2.4.4 Uplink FPORT~=4, History GNSS Positioning ===
59.2	429
66.2	430
155.2	431	Set [[PNACKMD=1>>\|\|anchor="H3.2.11A0A0AutoSendNone-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	432
66.2	433
66.3	434	(% style="color:red" %)Note for this mode:
59.2	435
59.3	436	* a) TrackerD will do an ACK check for data records sending to make sure every data arrive server.
103.1	437	* b) TrackerD will send data in CONFIRMED Mode when PNACKMD=1 and CFM=1, but TrackerD won't re-transmit the packet if it doesn't get ACK, it will just mark it as a NONE-ACK message. In a future uplink, if TrackerD gets an ACK, TrackerD will consider there is a network connection and resend all NONE-ACK Messages.
78.1	438	* c) the total payload will be 15 bytes, while US915/AU915 DR0 accepts only 11 bytes of payload. In this case (DR0 of US915/AU915), the payload on server will show NULL
50.2	439
59.3	440	The payload is 15 bytes, as below.
50.2	441
84.15	442	(% border="1.5" style="background-color:#ffffcc; color:green; width:500px" %)
66.2	443	\|=(% scope="row" %)(((
	444	Size(bytes)
	445	)))\|4\|4\|2\|1\|1\|1\|1\|1
66.3	446	\|=Value\|Latitude\|Longitude\|Year\|Month\|Day\|Hous\|Min\|Sen
59.3	447
146.1	448	[[image:image-20221009160309-2.png\|\|_mstalt="429312"]]
59.3	449
66.2	450
66.3	451	=== 2.4.5 Uplink FPORT~=6, BLE Positioning with Strongest iBeacon ===
59.3	452
84.2	453
81.1	454	TrackerD supports BLE scans for indoor positioning. User can set [[SMOD>>\|\|anchor="H3.2.7SetPositioningMode"]] to BLE pure or GPS/BLE hybrid so TrackerD will scan BLE iBeacon and find the strongest iBeacon info and uplink.
59.3	455
82.1	456	User can set [[BLEMASK>>\|\|anchor="H3.2.11A0SetBLEMASKtofilterBLEiBeacon"]] so TrackerD will only search the iBeacons which have UUID that match the BLEMASK settings.
79.1	457
81.1	458
51.25	459	(% border="1.5" cellspacing="3" style="background-color:#ffffcc; color:green; width:450px" %)
51.26	460	\|=(% scope="row" style="width: 60px;" %)(((
51.24	461	Size(bytes)
51.26	462	)))\|(% 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	463	\|=(% style="width: 50px;" %)Value\|(% style="width:44px" %)[[UUID>>\|\|anchor="HLocationinfo:"]]\|(% style="width:61px" %)(((
51.8	464	iBeacon MAJOR
51.11	465	)))\|(% style="width:63px" %)(((
	466	iBeacon MINOR
50.2	467	)))\|(% style="width:71px" %)(((
51.8	468	iBeacon Measured Power
51.11	469	)))\|(% style="width:50px" %)(((
51.8	470	iBeacon RSSI
51.11	471	)))\|(% style="width:47px" %)(((
51.8	472	[[Alarm & BAT>>\|\|anchor="HAlarm26BAT:"]]
51.11	473	)))\|(% style="width:15px" %)[[FLAG>>\|\|anchor="HFLAG:"]]
19.2	474
146.1	475	[[image:1664502425687-834.png\|\|_mstalt="296738"]]
19.2	476
	477
79.1	478	* (% style="color:#037691" %)BAT: (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV).
51.9	479	* (% style="color:#037691" %)MODE: (%%)Define the payload format.
	480	* (% style="color:#037691" %)UUID: (%%)The uuid from the strongest iBeacon.
	481	* (% style="color:#037691" %)MAJOR: (%%) The MAJOR from the strongest iBeacon.
114.1	482	* (% style="color:#037691" %)MINOR: (%%)The MINOR from the strongest iBeacon.
51.9	483	* (% style="color:#037691" %)Measured Power: (%%) The Measured Power from the strongest iBeacon.
	484	* (% style="color:#037691" %)RSSI: (%%) The RSSI from the strongest iBeacon.
19.2	485
155.3	486
	487
106.1	488	=== 2.4.6 Uplink FPORT~=8, WiFi Positioning with Strongest WiFi SSID（Since firmware 1.4.1） ===
105.2	489
84.19	490
109.1	491	TrackerD supports WiFi scans for indoor positioning. User can set [[SMOD>>\|\|anchor="H3.2.7SetPositioningMode"]] to WiFi so TrackerD will scan WiFi and find the strongest WiFi info and uplink.
19.3	492
50.2	493
86.1	494	(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:371.222px" %)
	495	\|=(% scope="row" style="width: 60px;" %)(((
	496	Size(bytes)
	497	)))\|(% style="width:60px" %)6\|(% style="width:60px" %)4\|(% style="width:79px" %)2\|(% style="width:66px" %)1
	498	\|=(% style="width: 69px;" %)Value\|(% style="width:76px" %)SSID\|(% style="width:87px" %)RSSI\|(% style="width:79px" %)(((
	499	[[Alarm & BAT>>\|\|anchor="HAlarm26BAT:"]]
	500	)))\|(% style="width:66px" %)[[FLAG>>\|\|anchor="HFLAG:"]]
19.2	501
86.1	502	(% class="wikigeneratedid" %)
146.1	503	[[image:1667288597595-714.png\|\|_mstalt="299598" height="212" width="1151"]]
86.1	504
	505
	506	* (% style="color:#037691" %)BAT: (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV).
	507	* (% style="color:#037691" %)SSID: (%%)WiFi name.
	508	* (% style="color:#037691" %)RSSI: (%%)The RSSI from the strongest WiFi.
	509
155.3	510
	511
86.1	512	=== 2.4.7 Add Payload format in TTN V3 ===
	513
	514
	515	In TTN V3, user can add a custom payload so it shows friendly.
	516
51.9	517	In the page (% style="color:#037691" %)Applications ~-~-> Payload Formats ~-~-> Custom ~-~-> decoder
19.2	518
	519
146.1	520	[[image:1664502649601-895.png\|\|_mstalt="296985"]]
50.2	521
51.9	522
143.2	523
78.7	524	Add the decoder from this link:
19.2	525
78.7	526	[[https:~~/~~/github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD>>https://github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD]]
19.2	527
	528	Save the change the uplink message will be parsed. As below:
	529
146.1	530	[[image:1664502676891-606.png\|\|_mstalt="296673"]]
19.2	531
	532
66.3	533	== 2.5 Integrate with Datacake ==
19.2	534
84.5	535
19.2	536	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.
	537
50.2	538	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	539
113.4	540
146.1	541	[[image:1664502695771-538.png\|\|_mstalt="297349"]]
19.2	542
50.2	543
66.3	544	== 2.6 Integrate with Tago ==
19.2	545
	546
81.1	547	After TrackerD sends data to LoRaWAN server such as TTN, user can pass the data to Datacake and plot out, currently only support GPS plot.
	548
19.2	549	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]]
	550
	551
146.1	552	[[image:1664502715371-321.png\|\|_mstalt="292162"]]
19.2	553
	554
68.4	555	== 2.7 Datalog Feature ==
56.1	556
68.4	557
78.1	558	total 273 entries,by default,
56.1	559
155.2	560	User can set [[PNACKMD=1>>\|\|anchor="H3.2.11A0A0AutoSendNone-ACKmessages"]], to enable Datalog feature.
68.4	561
71.1	562	Example use case.
68.4	563
146.1	564	[[image:image-20221009234703-2.png\|\|_mstalt="429143" height="328" width="899"]]
71.1	565
	566
146.1	567	[[image:image-20221009234629-1.png\|\|_mstalt="431145" height="390" width="577"]]
71.1	568
	569
66.3	570	== 2.8 Alarm Mode ==
19.2	571
	572
51.27	573	(((
51.11	574	User can push the (% style="color:red" %)RED button(%%) by more than 5 seconds to enter Alarm Mode.
51.27	575	)))
19.2	576
	577
51.27	578	(((
81.1	579	Once enter Alarm mode, the (% style="color:green" %)GREEN LED(%%) will flash 3 times, the buzzer will alarm for 5 seconds, then TrackerD will immediately send a packet without location info and then send a data packet with GPS positioning information. After that, the device will send 60 packets at 1-minute intervals. The Alarm flag in the payload will be set for the next 60 packets unless exits alert mode.
51.27	580	)))
19.2	581
	582
51.27	583	(((
143.2	584	Two ways to exit alarm mode:
51.27	585	)))
19.2	586
81.1	587	* Server sends a downlink command to exit.
19.2	588	* User fast press the RED button 10 times.
	589
51.27	590	(((
51.11	591	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	592	)))
19.2	593
	594
66.3	595	== 2.9 Transport Mode ==
19.2	596
	597
57.1	598	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	599
151.1	600	* [[MTDC>>\|\|anchor="H3.2.3SetTransportModePackettransmissioninterval"]] defines the Uplink Interval during transportation.
	601	* [[TDC>>\|\|anchor="H3.2.1SetTransmitInterval"]] defines the uplink interval when TrackerD is stactic.
153.1	602	* [[PT>>\|\|anchor="H3.2.16GetorSetThresholdformotiondetectFF08Sincefirmware1.4.3FF09"]] defines the threldhold to detect a motion.
55.1	603
155.3	604
	605
66.3	606	== 2.10 LED Status ==
19.2	607
	608
113.7	609	(% border="1.5" style="background-color:#ffffcc; width:500px" %)
51.27	610	\|=(% style="width: 150px;" %)Event\|=(% style="width: 200px;" %)Action\|=(% style="width: 150px;" %)AT+LON to control on/off
51.11	611	\|(% 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
	612	\|(% style="width:157px" %)Join request\|(% style="width:271px" %)(% style="color:green" %)Green (%%)led fast blink once (200ms)\|(% style="width:202px" %)Yes
	613	\|(% style="width:157px" %)Join Success\|(% style="width:271px" %)(% style="color:green" %)Green(%%) led on 5 second\|(% style="width:202px" %)N/A
	614	\|(% style="width:157px" %)Fixing Location\|(% style="width:271px" %)(% style="color:blue" %)BLUE (%%)blinks 200ms per second\|(% style="width:202px" %)Yes
113.7	615	\|(% style="width:157px" %)Fixed and uplink\|(% style="width:271px" %)(% style="color:green" %)GREEN (%%)blinks twice (200ms per blink)\|(% style="width:202px" %)Yes
51.11	616	\|(% style="width:157px" %)Fail Fix and uplink\|(% style="width:271px" %)(% style="color:red" %)RED (%%)blinks twice (200ms per blink)\|(% style="width:202px" %)Yes
	617	\|(% style="width:157px" %)Enter Alarm mode\|(% style="width:271px" %)(% style="color:red" %)RED (%%)on for 3 seconds\|(% style="width:202px" %)Yes
	618	\|(% style="width:157px" %)Uplink under Alarm\|(% style="width:271px" %)(% style="color:red" %)RED (%%)on for 1 second\|(% style="width:202px" %)Yes
	619	\|(% style="width:157px" %)Exit Alarm\|(% style="width:271px" %)(% style="color:blue" %)BLUE (%%)led on 5 second\|(% style="width:202px" %)Yes
	620	\|(% style="width:157px" %)Get Downlink\|(% style="width:271px" %)(% style="color:green" %)GREEN(%%) led on 1 second\|(% style="width:202px" %)Yes
	621	\|(% style="width:157px" %)Movement Detect\|(% style="width:271px" %)(% style="color:red" %)RED (%%)led on 500ms\|(% style="width:202px" %)N/A
19.2	622
155.3	623
155.4	624
66.3	625	== 2.11 Button Function ==
19.2	626
50.2	627
51.27	628	(% style="color:blue" %)RESET button:
19.2	629
146.1	630	[[image:1664502835802-546.png\|\|_mstalt="295061"]]
19.2	631
	632	Push this button will reboot the device. Device will exit alarm mode and re-join to LoRaWAN server.
	633
	634
51.11	635	(% style="color:red" %)RED button:
19.2	636
146.1	637	[[image:1664502854406-763.png\|\|_mstalt="295568"]]
19.2	638
	639
113.7	640	(% border="1" style="background-color:#ffffcc; width:510px" %)
84.18	641	\|=(% style="width: 100px;" %)Function\|=(% style="width: 205px;" %)Action\|=(% style="width: 205px;" %)Description
113.6	642	\|(% 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.8AlarmMode"]]
51.11	643	\|(% 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	644	\|(% 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	645
155.3	646
155.4	647
66.3	648	== 2.12 USB Port Function ==
19.2	649
50.2	650
19.2	651	The USB interface of TrackerD has below functions:
	652
	653	* Power on the device
	654	* Recharge the battery
51.11	655	* [[Configure Device>>\|\|anchor="H3.ConfigureTrackerDviaATcommandorLoRaWANdownlink"]]
	656	* [[Upgrade Firmware>>\|\|anchor="H5.UploadFirmware"]]
19.2	657
155.3	658
	659
19.3	660	= 3. Configure TrackerD via AT command or LoRaWAN downlink =
19.2	661
	662
	663	User can configure TrackerD via AT Command or LoRaWAN Downlink.
	664
51.13	665	LoRaWAN Downlink instruction for different platforms: [[IoT LoRaWAN Server>>doc:Main.WebHome]]
19.2	666
	667
19.3	668	== 3.1 Access AT Command ==
19.2	669
	670
50.2	671	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	672
	673
146.1	674	[[image:1664502999401-486.png\|\|_mstalt="296985"]]
50.2	675
	676
51.11	677	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	678
	679
146.1	680	[[image:1664503022490-662.png\|\|_mstalt="293332"]]
19.2	681
	682
146.1	683	[[image:1664503035713-500.png\|\|_mstalt="291096"]]
19.2	684
	685
146.1	686	[[image:1664503047675-651.png\|\|_mstalt="295386"]]
50.2	687
	688
19.3	689	== 3.2 Command Set ==
19.2	690
19.3	691	=== 3.2.1 Set Transmit Interval ===
19.2	692
50.2	693
19.2	694	Set device uplink interval.
	695
51.13	696	* (% style="color:blue" %)AT Command:
19.2	697
51.13	698	(% style="color:#037691" %)AT+TDC=xxx
19.2	699
50.2	700	Example: AT+TDC=300000. Means set interval to 5 minutes(300 seconds)
19.2	701
	702
51.13	703	* (% style="color:blue" %)Downlink Payload (prefix 0x01):
19.2	704
51.13	705	(% style="color:#037691" %)0x01 00 01 2C (%%) ~/~/ Same as AT+TDC=300000
19.2	706
	707
19.3	708	=== 3.2.2 Set Alarm Packet transmission interval ===
19.2	709
50.2	710
19.2	711	Set alarm packet transmit interval
	712
51.13	713	* (% style="color:blue" %)AT Command:
19.2	714
51.13	715	(% style="color:#037691" %)AT+ATDC=xx.
19.2	716
51.2	717	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	718
	719
51.13	720	* (% style="color:blue" %)Downlink Payload (prefix 0xB1):
19.2	721
51.13	722	(% style="color:#037691" %)0xB1 00 00 3C (%%) ~/~/ Same as AT+ATDC=60000
19.2	723
	724
57.1	725	=== 3.2.3 Set Transport Mode Packet transmission interval ===
50.2	726
	727
57.1	728	Set Transport Mode packet transmit interval
19.2	729
51.13	730	* (% style="color:blue" %)AT Command:
19.2	731
51.13	732	(% style="color:#037691" %)AT+MTDC=xx.
19.2	733
57.1	734	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	735
	736
51.13	737	* (% style="color:blue" %)Downlink Payload (prefix 0x03):
19.2	738
111.1	739	(% style="color:#037691" %)0x03 00 01 2C (%%) ~/~/ Same as AT+MTDC=3000000
19.2	740
	741
50.2	742	=== 3.2.4 Exit Alarm ===
19.2	743
50.2	744
19.2	745	Server send downlink command to exit Alarm mode
	746
51.13	747	* (% style="color:blue" %)AT Command: No AT Command
19.2	748
51.13	749	* (% style="color:blue" %)Downlink Payload (prefix 0x02):
19.2	750
51.13	751	(% style="color:#037691" %)0x02 01 (%%) ~/~/ Exit Alarm Mode
19.2	752
51.13	753
50.2	754	=== 3.2.5 Disable/Enable LED flash ===
	755
	756
19.2	757	Disable/Enable LED for position, downlink and uplink
	758
51.13	759	* (% style="color:blue" %)AT Command:
19.2	760
51.13	761	(% style="color:#037691" %)AT+LON=xx. (Disable (0), Enable (1), default:1)
19.2	762
51.28	763	Example: AT+LON=0 ~-~-> Disable LED for position, downlink and uplink.
19.2	764
	765
51.13	766	* (% style="color:blue" %)Downlink Payload (prefix 0xAE):
19.2	767
51.13	768	(% style="color:#037691" %)0xAE 00 (%%) ~/~/ Same as AT+LON=0
19.2	769
	770
59.1	771	=== 3.2.6 Disable/Enable Transport Mode ===
19.2	772
	773
59.1	774	Users can use this feature to enable/disable Transport Mode.
19.2	775
51.13	776	* (% style="color:blue" %)AT Command:
19.2	777
51.13	778	(% style="color:#037691" %)AT+INTWK=xx. (Disable (0), Enable (1), default:0)
19.2	779
111.1	780	Example: AT+INTWK=1 ~-~-> Enable Transport Mode.
19.2	781
	782
51.13	783	* (% style="color:blue" %)Downlink Payload (prefix 0xAF):
19.2	784
111.1	785	(% style="color:#037691" %)0xAF 01 (%%) ~/~/ Same as AT+INTWK=1
19.2	786
	787
50.2	788	=== 3.2.7 Set Positioning Mode ===
19.2	789
50.2	790
79.1	791	SMOD define how TrackerD scan and uplink data:
19.2	792
	793
51.13	794	* (% style="color:blue" %)AT Command:
19.2	795
74.5	796	(% style="color:#037691" %)AT+SMOD=aa,bb,cc
19.2	797
60.2	798	(% style="color:#037691" %) aa:
19.2	799
87.1	800	* (% style="color:red" %)1: GPS ONLY(Factory Settings): (%%)Only get and uplink GPS location info.
113.3	801
88.1	802	* (% style="color:red" %)2: BLE or WiFi ONLY: (%%)Only obtain iBeacon info via BLE and uplink or obtain WiFi ssid info via WiFi and uplink. Design for Indoor tracking.
113.3	803
113.4	804	* (% style="color:red" %)3: GPS/BLE Hybrid: (%%)Combination for Indoor and Outdoor tracking.Devices will try to search BLE iBeacon first. If device can't find the iBeacon, it will use GPS for positioning.
60.2	805
	806	(% style="color:#037691" %)bb:
	807
74.5	808	* (% style="color:red" %)0 : (%%)GPS+ BAT+ State+Tem&Hum
113.2	809
74.5	810	* (% style="color:red" %)1 :(%%) GPS +BAT State
60.2	811
74.5	812	(% style="color:#037691" %)cc:
60.2	813
147.1	814	* (% _mstmutation="1" style="color:red" %)1 : (%%) (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State
113.2	815
146.1	816	* (% _mstmutation="1" style="color:red" %)2 : (%%) (WiFi)SSID+Rssi+BAT+State ((% _mstmutation="1" style="color:#037691" %)V1.4.1 Version support this function later(%%))
60.2	817
74.5	818	(% style="color:blue" %)Example:
19.2	819
111.1	820	AT+SMOD=1,0,0 ~-~-> GPS+ BAT+ State+Tem&Hum
113.2	821
111.1	822	AT+SMOD=1,1,0 ~-~-> GPS +BAT State
113.2	823
111.1	824	AT+SMOD=2,0,1 ~-~-> (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State
113.2	825
111.1	826	AT+SMOD=2,0,2 ~-~-> (WiFi)SSID+Rssi+BAT+State
19.2	827
	828
51.13	829	* (% style="color:blue" %)Downlink Payload (prefix 0xA5):
19.2	830
111.1	831	(% style="color:#037691" %)0xA5 01 00 00 (%%) ~/~/ Same as AT+SMOD=1,0,0
19.2	832
	833
50.2	834	=== 3.2.8 Set MAX GPS position time ===
	835
	836
19.2	837	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.
	838
	839
143.2	840	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.
19.2	841
	842
51.13	843	* (% style="color:blue" %)AT Command:
19.2	844
51.13	845	(% style="color:#037691" %)AT+FTIME=xx (%%) ~-~-> Set to use xx as max fix time.
19.2	846
74.5	847	Example: AT+FTIME=150
19.2	848
	849
51.13	850	* (% style="color:blue" %)Downlink Payload (prefix 0xAA):
19.2	851
51.13	852	(% style="color:#037691" %)0xAA 00 96 (%%) ~/~/ Set AT+FTIME=150
19.2	853
	854
68.4	855	=== 3.2.9 Set PDOP value for GPS fix accuracy ===
19.2	856
	857
50.2	858	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	859
50.2	860
19.2	861	A GPS packet with lower PDOP has higher accuracy. PDOP default value is 2.0
	862
	863
51.13	864	* (% style="color:blue" %)AT Command:
19.2	865
51.13	866	(% style="color:#037691" %)AT+PDOP=2.5 (%%) ~-~-> Set PDOP to 2.5
19.2	867
	868
51.13	869	* (% style="color:blue" %)Downlink Payload (prefix 0xAD):
19.2	870
51.13	871	(% style="color:#037691" %)0xAD 00 0A (%%) ~/~/ Set AT+PDOP=1 (0x0A / 10 =1)
19.2	872
51.13	873	(% style="color:#037691" %)0xAD 00 19 (%%) ~/~/ Set AT+PDOP=2.5 (0x19 / 10 =2.5)
19.2	874
51.13	875	(% style="color:#037691" %)0xAD 00 46 (%%) ~/~/ Set AT+PDOP=7 (0x46 / 10 =7)
19.2	876
50.2	877
51.12	878
155.3	879	=== 3.2.10 Disable/Enable the confirmation mode ===
19.2	880
155.4	881
51.13	882	* (% style="color:blue" %)AT Command:
19.2	883
74.6	884	(% style="color:#037691" %)AT+CFM=xx
19.2	885
	886
50.2	887	~ Example:
19.2	888
107.1	889	AT+CFM=0 ~-~-> Disable confirmation
19.2	890
107.1	891	AT+CFM=1 ~-~-> Enable confirmation
19.2	892
50.2	893
51.13	894	* (% style="color:blue" %)Downlink Payload (prefix 0x05):
19.2	895
111.1	896	(% style="color:#037691" %)0x05 01 (%%) ~/~/ Same as AT+CFM=1
19.2	897
	898
148.1	899	=== 3.2.11 Auto Send None-ACK messages ===
74.6	900
	901
	902	TrackerD will wait for ACK for each uplink, If TrackerD doesn't get ACK from the IoT server, it will consider the message doesn't arrive server and store it. TrackerD keeps sending messages in normal periodically. Once TrackerD gets ACK from a server, it will consider the network is ok and start to send the not-arrive message.
	903
	904
	905	* (% style="color:blue" %)AT Command: AT+PNACKMD
	906
	907	The default factory setting is 0.
	908
	909
	910	Command Example Function Response:
	911
	912	(% style="color:#037691" %)AT+PNACKMD=1 (%%) ~/~/ Poll None-ACK message OK
	913
	914
	915	* (% style="color:blue" %)Downlink Command: 0x34
	916
148.1	917	Example: 0x34 01 ~/~/ Same as AT+PNACKMD=1
74.6	918
	919
148.1	920	=== 3.2.12 Set BLEMASK to filter BLE iBeacon ===
80.1	921
84.2	922
86.1	923	BLEMASK is to filter the unwanted BLE iBeacons during scan. For example, if BLEMASK is 123456. TrackerD will only uplink UUID info which includes 123456. It will ignore all other iBeacons which doesn’t contact 123456 in the UUID.
80.1	924
84.5	925	(% style="color:red" %)Note: BLEMASK range is 6 ~~ 10 bytes. If AT+BLEMASK < 6 bytes, BLEMASK will be disabled.
80.1	926
84.5	927	(% style="color:blue" %)AT Command:
80.1	928
146.1	929	(% _mstmutation="1" style="color:#037691" %)AT+BLEMASK=123456 (%%) ~/~/ Set BLEMASK = 123456
80.1	930
146.1	931	(% _mstmutation="1" style="color:#037691" %)AT+BLEMASK=0 (%%) ~/~/ disable BLEMASK
80.1	932
100.1	933	(% style="color:blue" %)Downlink Payload: (Prefix : 0xB2)(Since firmware 1.4.1）
84.5	934
148.1	935	Example: 0xB2 01 02 03 04 05 06 ~/~/ Set BLEMASK to 123456
100.1	936
105.2	937
148.1	938	=== 3.2.13 Set WiFIMASK to filter WiFi SSID（Since firmware 1.4.1） ===
84.5	939
86.1	940
108.1	941	WiFiMASK is to filter the unwanted WiFi SSID during scan. For example, if WiFiMASK is 123456. TrackerD will only uplink SSID info which includes 123456 as prefix. It will ignore all other WiFi which doesn’t contact 123456 in the SSID.
86.1	942
	943	(% style="color:red" %)Note: WiFiMASK range is 6 ~~ 10 bytes. If AT+ WiFiMASK < 6 bytes, WiFiMASK will be disabled.
	944
	945	(% style="color:blue" %)AT Command:
	946
146.1	947	(% _mstmutation="1" style="color:#037691" %)AT+WiFiMASK=123456 (%%) ~/~/ Set WiFiMASK = 123456
86.1	948
146.1	949	(% _mstmutation="1" style="color:#037691" %)AT+WiFiMASK=0 (%%) ~/~/ disable WiFiMASK
86.1	950
100.1	951	(% style="color:blue" %)Downlink Payload: (Prefix : 0xB3)(Since firmware 1.4.1）
86.1	952
148.1	953	Example: 0xB3 01 02 03 04 05 06 ~/~/ Set WiFiMASK to 123456
100.1	954
105.2	955
148.1	956	=== 3.2.14 Disable/Enable Information printing（Since firmware 1.4.1） ===
98.1	957
	958
	959	Users can use this feature to enable/disable Information printing.
	960
	961	(% style="color:blue" %)AT Command:
	962
106.1	963	(% style="color:#037691" %)AT+SHOWID=XX (%%) ~/~/(Disable (0), Enable (1), default:0)
111.1	964	\\Example: AT+SHOWID=1 ~-~-> Enable Information printing.
98.1	965
	966
148.1	967	=== 3.2.15 Get or Set Eight Channels Mode, only for us915, AU915（Since firmware 1.4.1） ===
104.1	968
105.2	969
104.1	970	The Channels Mode in the LORAWAN LMIC library is from 0 ~~ 7. When CHE = 8, 72 channels will be accessible to the network.
	971
	972	(% style="color:blue" %)AT Command:
	973
113.2	974	(% style="color:#037691" %)AT+CHE=1(%%) ~/~/ set one channels mode
104.1	975
113.2	976
113.4	977	(% style="color:blue" %)Downlink Payload:0X24
113.2	978
111.1	979	Example: 0x24 01 ~/~/ Same as AT+CHE=1
104.1	980
	981
152.1	982	=== 3.2.16 Get or Set Threshold for motion detect（Since firmware 1.4.3） ===
	983
	984	User can set the motion detect thredhold for transportation mode. The smaller the value, the more sensitivity to trigger a motion event.
	985
	986	(% style="color:blue" %)AT Command:
	987
	988	(% style="color:#037691" %)AT+PT=xx
	989
	990	Example:
	991
	992	AT+PT=14 ~-~-> Set to detect car motion.
	993
	994	AT+PT=41 ~-~-> set to detect walk motion.
	995
	996
	997	(% style="color:blue" %)Downlink Payload:0xB4(%%)
	998	0xB4 14 ~/~/ Same as AT+PT=14
	999
	1000
	1001
19.4	1002	= 4. Setting for Different Scenarios =
19.2	1003
	1004
	1005
19.4	1006	= 5. Upload Firmware =
19.2	1007
19.4	1008	== 5.1 Firmware Change Log ==
	1009
50.2	1010
19.2	1011	[[See this link>>url:https://github.com/dragino/TrackerD]]
	1012
	1013
19.4	1014	== 5.2 How to upgrade firmware ==
19.2	1015
	1016
50.2	1017	User can use the TrackerD's USB port to upgrade firmware into it. The hardware connection for upgrade firmware is as below:
19.2	1018
	1019
50.2	1020	(% style="color:blue" %)Step1: (%%)Connect TrackerD and PC via USB cable shipped with TrackerD.
19.2	1021
50.2	1022
	1023	(% style="color:blue" %)Step2: (%%) Install CH9102 driver in the PC.
	1024
19.2	1025	After installation of the driver and plug in TrackerD, user should be able to see com port in PC's device manager.
	1026
	1027
51.28	1028	(% 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	1029
	1030
50.2	1031	(% style="color:blue" %)Step4: (%%) Run Flash Download Tool and configure chip type to ESP32
19.2	1032
	1033
146.1	1034	[[image:1664503563660-578.png\|\|_mstalt="296777"]]
19.2	1035
	1036
146.1	1037	[[image:1664503574618-659.png\|\|_mstalt="297986"]]
19.2	1038
50.2	1039
84.2	1040
50.2	1041	(% style="color:blue" %)Step5: (%%) Select the firmware file (.bin format), com port and proper SPI configure. Clink Start. Bin file location:
	1042
73.1	1043	[[https:~~/~~/github.com/dragino/TrackerD/releases>>https://github.com/dragino/TrackerD/releases]]
19.2	1044
	1045
143.2	1046	Users need to use below files:
19.2	1047
	1048	boot_app0.bin @0e000
	1049
131.1	1050	US915.bin @ 0x10000(Select the bin file of the frequency band you need)
19.2	1051
	1052
146.1	1053	[[image:image-20221118105220-2.png\|\|_mstalt="426608"]]
19.2	1054
	1055
	1056
50.2	1057	After upgrade finish, it will show finish as below:
19.2	1058
146.1	1059	[[image:image-20221118105402-4.png\|\|_mstalt="427986"]]
19.2	1060
	1061
50.2	1062
19.4	1063	= 6. Developer Guide =
19.2	1064
19.4	1065	== 6.1 Compile Source Code ==
	1066
	1067	=== 6.1.1 Set up ARDUINO compile environment ===
	1068
	1069
51.28	1070	* 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	1071
51.15	1072	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	1073
	1074
146.1	1075	[[image:1664503635019-941.png\|\|_mstalt="294658"]]
19.2	1076
50.2	1077
68.4	1078
51.28	1079	* (% style="color:#037691" %)Go to tools ~-~-> Boards ~-~-> Boards Manager,(%%) find the esp32 information and install it.
19.2	1080
146.1	1081	[[image:1664503715811-892.png\|\|_mstalt="295698"]]
19.2	1082
	1083
84.3	1084	(% id="cke_bm_4554S" style="display:none" %) (%%)Find the path of SP32 installation, find the file as shown in Figure 1, and change the SPI pin to the shown in Figure 2.
19.2	1085
146.1	1086	[[image:image-20221024105643-1.png\|\|_mstalt="428129"]]
84.3	1087
84.4	1088	~ Figure1
84.3	1089
	1090
146.1	1091	[[image:image-20221024105643-2.png\|\|_mstalt="428493"]]
84.3	1092
84.4	1093	Figure2
84.3	1094
	1095
51.28	1096	* Download the latest TrackerD from the dragino github: [[https:~~/~~/github.com/dragino/TrackerD>>url:https://github.com/dragino/TrackerD]]
19.2	1097
50.2	1098	Put the Library in the TrackerD directory into the libraries file in the Arduino directory:
19.2	1099
	1100
146.1	1101	[[image:1664503752288-974.png\|\|_mstalt="298194"]]
19.2	1102
50.2	1103
19.4	1104	== 6.2 Source Code ==
	1105
	1106
51.16	1107	* (% style="color:blue" %)Open the example in the TrackerD file, please select the correct port in the IDE, as shown below:
19.2	1108
146.1	1109	[[image:1664503794261-827.png\|\|_mstalt="296387"]]
19.2	1110
	1111
	1112
51.16	1113	* (% style="color:blue" %)Click to upload
19.2	1114
146.1	1115	[[image:1664503808294-336.png\|\|_mstalt="295711"]]
19.2	1116
	1117
	1118
51.16	1119	* (% style="color:blue" %)Check the result, if the upload is successful, as shown below, open the serial port to view the data
19.2	1120
146.1	1121	[[image:1664503824081-592.png\|\|_mstalt="294918"]] [[image:1664503831430-500.png\|\|_mstalt="290784"]]
19.2	1122
	1123
18.2	1124	= 7. FAQ =
15.2	1125
18.2	1126	== 7.1 How to change the LoRa Frequency Bands/Region? ==
14.1	1127
	1128
51.14	1129	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	1130
12.1	1131
18.2	1132	== 7.2 What is the pin mapping for the USB program cable? ==
2.1	1133
7.1	1134
146.1	1135	[[image:1664499635206-262.png\|\|_mstalt="295360"]]
7.1	1136
	1137
	1138
51.28	1139	(% border="1.5" cellspacing="3" style="background-color:#ffffcc; color:green; width:314px" %)
51.27	1140	\|=(% style="width: 118px;" %)Pin\|=(% style="width: 67px;" %)Color\|=(% style="width: 123px;" %)USB Pin
18.2	1141	\|(% style="width:118px" %)A4,B4,A9,B9\|(% style="width:67px" %)Red\|(% style="width:123px" %)VCC
	1142	\|(% style="width:118px" %)A7,B7\|(% style="width:67px" %)White\|(% style="width:123px" %)D- (N/A)
	1143	\|(% style="width:118px" %)A6,B6\|(% style="width:67px" %)Green\|(% style="width:123px" %)D+(N/A)
	1144	\|(% style="width:118px" %)A1,B1,A12,B12\|(% style="width:67px" %)Black\|(% style="width:123px" %)GND
	1145	\|(% style="width:118px" %)A5\|(% style="width:67px" %)Purple\|(% style="width:123px" %)MTDC/GOIO13
	1146	\|(% style="width:118px" %)B5\|(% style="width:67px" %)Blue\|(% style="width:123px" %)MTDC/GPIO12
	1147	\|(% style="width:118px" %)A8\|(% style="width:67px" %)Yellow\|(% style="width:123px" %)MTMS/GPIO14
	1148	\|(% style="width:118px" %)B8\|(% style="width:67px" %)Grey\|(% style="width:123px" %)MTDO/GPIO15
7.1	1149
155.3	1150
155.4	1151
97.1	1152	== 7.3 Notes on using different serial port tools for TrackerD ==
	1153
113.4	1154	=== 7.3.1 Serial port utility ===
97.1	1155
	1156
	1157	Serial port utility requires you to automatically add data streams.
	1158
	1159	Need to adjust the data stream to RTS/CTS on physical restart.
	1160
	1161	(% class="wikigeneratedid" %)
146.1	1162	[[image:image-20221102140621-1.png\|\|_mstalt="425672"]]
97.1	1163
	1164
143.2	1165
97.1	1166	When using AT commands, the data flow needs to be adjusted to XON/XOFF
	1167
146.1	1168	[[image:image-20221102140638-2.png\|\|_mstalt="428727"]]
97.1	1169
	1170
113.4	1171	=== 7.3.2 SecureCRT ===
97.1	1172
	1173
	1174	The default command window of SecureCRT is not displayed. Entering a command requires a complete input of the entire command. You can open the command window in the view.
	1175
	1176
146.1	1177	[[image:image-20221102140704-3.png\|\|_mstalt="427076"]]
97.1	1178
	1179
146.1	1180	[[image:image-20221102140712-4.png\|\|_mstalt="427089"]]
97.1	1181
	1182
113.4	1183	=== 7.3.3 PUTTY ===
97.1	1184
	1185
146.1	1186	[[image:image-20221102140748-5.png\|\|_mstalt="430456"]]
97.1	1187
	1188
	1189	Since putty does not have a command window, you need to fill in the complete command externally, and then copy it to putty.The information copied outside can be pasted by right-clicking the mouse in putty.
	1190
	1191
146.1	1192	[[image:image-20221102140801-6.png\|\|_mstalt="427466"]]
97.1	1193
98.2	1194
123.1	1195	== 7.4 How to modify source code to compile different frequency band bin file? ==
113.4	1196
133.1	1197
	1198	(% class="box infomessage" %)
	1199	(((
135.1	1200	(% style="color:red" %)Important(%%): Developer MUST follow the Arduino Environment Instruction exactly include change the SPI pin mappings.
134.1	1201	See : [[Set Up Arduino Compile Environment for TrackerD. >>\|\|anchor="H6.1.1SetupARDUINOcompileenvironment"]]
133.1	1202	)))
	1203
143.2	1204	~1. When compiling the frequency band, you need to find LMIC_PROJECT_CONFIG.H file.
122.1	1205
143.2	1206
146.1	1207	[[image:image-20221116111844-1.png\|\|_mstalt="428688" height="227" width="782"]]
122.1	1208
	1209
143.2	1210
	1211	2. Open LMIC_PROJECT_CONFIG.H, find the corresponding macro definition and open it(AS923_2,AS923_3,AS923_4 except).
	1212
	1213
146.1	1214	[[image:image-20221116111844-2.png\|\|_mstalt="429052" height="262" width="781"]]
122.1	1215
	1216
143.2	1217
	1218	3. Compile the AS923_JP band, please refer to the intention shown
	1219
	1220
146.1	1221	[[image:image-20221116111844-3.png\|\|_mstalt="429416" height="338" width="746"]]
122.1	1222
	1223
143.2	1224
	1225	4. In other frequency bands in AS923, you need to find Lorabase_as923.H, path arduino-lmic \ src \ lmic, as shown in the figure below.
	1226
	1227
146.1	1228	[[image:image-20221116111844-4.png\|\|_mstalt="429780" height="641" width="739"]]
122.1	1229
143.2	1230
146.1	1231	[[image:image-20221116111844-5.png\|\|_mstalt="430144" height="551" width="708"]]
122.1	1232
	1233
110.1	1234	= 8 Trouble Shooting =
98.2	1235
113.4	1236	== 8.1 TDC is changed to 4294947296 and cause no uplink. ==
	1237
	1238
	1239	(((
155.4	1240	Before firmware v1.4.0: When the Transport Mode is enabled ((% style="color:blue" %)AT+INTWK=1(%%)), the TDC needs to be greater than MTDC, otherwise, TDC setting will because 4294947296 after wakre up from motion. This bug is fixed in firmware v1.4.1
113.4	1241	)))
105.1	1242
105.2	1243
113.4	1244	== 8.2 Device not able get AT Command or show output after wake up from deep sleep mode ==
	1245
	1246
	1247	(((
110.1	1248	ESP32 is not able to accept the Interrupt from UART after wake up from deep sleep mode. User need to press the button (one click) and trackerD will be able to accept UART command, it there is no action in UART for 15 seconds. it will go to deep sleep mode.
113.4	1249	)))
7.1	1250
	1251
136.1	1252	== 8.3 Problem after Upgrading Firmware ==
113.4	1253
155.3	1254	=== 8.3.1 "rst: (0x3 SW_RESET)" and Continue Restart after upgrading ===
113.4	1255
136.1	1256
155.4	1257	Error Output
	1258
	1259
154.1	1260	[[image:image-20221122100004-4.png\|\|_mstalt="424606"]]
	1261
155.4	1262
113.4	1263	(((
154.1	1264	Some partition is missed during upgrade, please upgrade below four files as example:
	1265
	1266	[[image:image-20221122100004-2.png\|\|_mstalt="423878" height="619" width="389"]]
113.4	1267	)))
113.1	1268
113.4	1269
155.3	1270	=== 8.3.2 TrackerD's led light is always GREEN on after upgrading ===
113.1	1271
	1272
136.1	1273	It is because the partitions are different when upgrading versions above 1.4.1, and a new partition file needs to be added. Please refer to the operation steps in chapter 8.3.1
114.1	1274
	1275
155.3	1276	=== 8.3.3 "flash read err" after upgrade firmware ===
143.2	1277
155.4	1278
144.1	1279	Error shows below, user might erase the entire flash include u-boot partition which cause this issue.
142.1	1280
155.4	1281
146.1	1282	[[image:image-20221122100004-1.png\|\|_mstalt="423514" height="497" width="534"]]
142.1	1283
	1284
144.1	1285	User need to upgrade again with below four files to solve this issue.
143.2	1286
146.1	1287	[[image:image-20221122100004-2.png\|\|_mstalt="423878" height="619" width="389"]]
142.1	1288
143.2	1289	Figure 2
142.1	1290
143.2	1291
155.4	1292	=== 8.3.4 "Device Key become ff ff ff ff ff ff ff ff " after upgrade firmware ===
143.2	1293
155.4	1294
144.1	1295	User might erase the entire flash include keys and default settings which cause this issue.
	1296
155.4	1297	After the upgrade is completed, enter AT+CFG as shown in the figure below.
142.1	1298
155.4	1299
146.1	1300	[[image:image-20221122100004-3.png\|\|_mstalt="424242"]]
142.1	1301
	1302
155.4	1303	Please (% style="color:blue" %)AT+FDR(%%) which will reset all settings to factory settings. , and then input the following keys by the information on the label.
	1304
147.1	1305	After AT+FDR. please set
142.1	1306
155.4	1307	* (% _mstmutation="1" style="color:blue" %)AT+PDOP=7
155.3	1308
155.4	1309	* (% _mstmutation="1" style="color:blue" %)AT+FTIME=180000
147.1	1310
155.4	1311	Example:
144.1	1312
146.1	1313	AT+PDOP=7.00
	1314
	1315	AT+FTIME=180
	1316
144.1	1317	AT+DEUI=70B3D57ED0053981
	1318
142.1	1319	AT+APPEUI=D23345667BCBCCAF
	1320
	1321	AT+APPKEY=F402A1A7A350445A7CD2DEA95511BFA1
	1322
144.1	1323	AT+DADDR=260b4dce ( no need for OTAA)
142.1	1324
144.1	1325	AT+NWKSKEY=71cb7672441f573a53d4f34d307fc61d ( no need for OTAA)
142.1	1326
144.1	1327	AT+APPSKEY=dacce2299ecd97a73ee3f80b5a46a559 ( no need for OTAA)
142.1	1328
	1329
143.2	1330	== 8.4 When positioning, it will restart or the PDOP setting is unsuccessful ==
142.1	1331
143.2	1332
142.1	1333	Please download version 1.4.2 again
	1334
	1335
143.2	1336	== 8.5 How to deal with unsuccessful GPS positioning? ==
116.1	1337
143.2	1338
	1339	1） Make Sure the device is in Open Area where can see the sky.
	1340
116.1	1341	2) Set PDOP to a higher value.
	1342
148.1	1343	* (% _mstmutation="1" style="color:blue" %)AT+PDOP=2 (%%)(can be positioned precisely.）
132.1	1344
148.1	1345	* (% _mstmutation="1" style="color:blue" %)AT+PDOP=7 (%%)(Quickly locate in open spaces）
132.1	1346
148.1	1347	* (% _mstmutation="1" style="color:blue" %)AT+PDOP=14.7 (%%)(Positioning can be acquired in complex environments）
132.1	1348
116.1	1349	Please refer to this [[link>>http://wiki.dragino.com/xwiki/bin/view/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/TrackerD/#H3.2.9SetPDOPvalueforGPSfixaccuracy]] on how to set up PDOP
	1350
	1351
110.1	1352	= 9. Order Info =
	1353
	1354
15.6	1355	Part Number: (% style="color:blue" %)TrackerD-XXX
8.1	1356
15.6	1357	(% style="color:blue" %)XXX(%%): The default frequency band
8.1	1358
15.6	1359	* (% style="color:red" %)EU433(%%): Default frequency band EU433
143.2	1360
15.6	1361	* (% style="color:red" %)EU868(%%): Default frequency band EU868
143.2	1362
15.6	1363	* (% style="color:red" %)IN865(%%): Default frequency band IN865
143.2	1364
15.6	1365	* (% style="color:red" %)KR920(%%): Default frequency band KR920
143.2	1366
15.6	1367	* (% style="color:red" %)AS923(%%): Default frequency band AS923
143.2	1368
15.6	1369	* (% style="color:red" %)AU915(%%): Default frequency band AU915
143.2	1370
15.6	1371	* (% style="color:red" %)US915(%%): Default frequency band US915
15.2	1372
155.3	1373
	1374
110.1	1375	= 10. Packing Info =
18.2	1376
	1377
51.30	1378	(% style="color:#037691" %)Package Includes:
8.1	1379
50.3	1380	* TrackerD LoRaWAN GPS/BLE Tracker x 1
143.2	1381
50.3	1382	* USB recharge & program cable x 1
12.1	1383
51.30	1384	(% style="color:#037691" %)Dimensions and Weight:
12.1	1385
98.2	1386	* Device Size: 85 x 48 x 15 mm
143.2	1387
50.3	1388	* Weight: 50g
15.6	1389
155.3	1390
	1391
110.1	1392	= 11. Support =
18.2	1393
50.3	1394
18.2	1395	* 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.
143.2	1396
51.28	1397	* 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	1398
155.3	1399
	1400
110.1	1401	= 12. Reference =
18.2	1402
	1403
12.1	1404	* [[Firmware in Bin format>>https://www.dropbox.com/sh/733s8xlwahhqg1d/AABxDz80lBVX_to8zNuUQWFja?dl=0]]
143.2	1405
12.1	1406	* [[Source Code>>https://github.com/dragino/TrackerD]]
143.2	1407
12.1	1408	* [[Hardware Source>>https://www.dropbox.com/sh/orwoy6cecb89m4e/AAD37sRuUrvKsHgAJxuVTkB5a?dl=0]]
155.4	1409	)))

Wiki source code of TrackerD -LoRaWAN Tracker User Manual

Applications

Navigation