TrackerD -LoRaWAN Tracker User Manual

TrackerD is an (% style="color:blue" %)**Open Source LoRaWAN Tracker**(%%) based on (% style="color:blue" %)**ESP32 MCU**(%%) and (% style="color:blue" %)**Semtech LoRa Wireless Chip**.

23

)))

24

25

(((

26

In TrackerD, there are various sensors such as GPS, WiFi, BLE, Temperature, Humidity, Motion Detection, and Buzzer. User can use TrackerD for different tracking scenario.

27

28

(((

29

TrackerD is program friendly. Developers can use Arduino IDE to customize the software of TrackerD to fit their IoT solution.

)))

(((

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.

)))

(((

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.

38

)))

39

40

[[image:1664499921684-770.png||_mstalt="298194"]]

41

42

43

(% style="color:red" %)**Note: LoRaWAN server can be a general LoRaWAN server other than TTN.**

44

45

46

== 1.2 Specifications ==

47

48

49

(% style="color:blue" %)**Micro Controller:**

50

51

* Espressif ESP32 PICO D4

52

* MCU: ESP32 PICO D4

53

* Bluetooth: Bluetooth V4.2 BR/EDR and Bluetooth LE

54

* WiFi : 802.11 b/g/n (802.11n up to 150 Mbps)

55

* Integrated SPI flash : 4 MB

* RAM: 448 KB

* EEPROM: 520 KB

* Clock Speed: 32Mhz

(% style="color:blue" %)**Common DC Characteristics:**

61

62

* Supply Voltage: 5V via USB port or Internal li-on battery

63

* Operating Temperature: -40 ~~ 60°C

64

65

(% style="color:blue" %)**LoRa Spec:**

66

67

* Frequency Range,

68

** Band 1 (HF): 862 ~~ 1020 Mhz

69

* 168 dB maximum link budget.

70

* +20 dBm - 100 mW constant RF output vs.

71

* +14 dBm high efficiency PA.

72

* Programmable bit rate up to 300 kbps.

73

* High sensitivity: down to -148 dBm.

74

* Bullet-proof front end: IIP3 = -12.5 dBm.

75

* Excellent blocking immunity.

76

* Low RX current of 10.3 mA, 200 nA register retention.

77

* Fully integrated synthesizer with a resolution of 61 Hz.

78

* FSK, GFSK, MSK, GMSK, LoRaTM and OOK modulation.

79

* Built-in bit synchronizer for clock recovery.

80

* Preamble detection.

81

* 127 dB Dynamic Range RSSI.

82

* Automatic RF Sense and CAD with ultra-fast AFC.

83

* Packet engine up to 256 bytes with CRC.

84

* LoRaWAN 1.0.3 Specification

85

86

(% style="color:blue" %)**Battery:**

87

88

* 1000mA Li-on Battery power (for model TrackerD)

89

90

(% style="color:blue" %)**Power Consumption**

91

92

* Sleeping Mode: 200uA

93

* LoRa Transmit Mode: 125mA @ 20dBm 44mA @ 14dBm

94

* Tracking: max: 38mA

== 1.3 Features ==

* LoRaWAN 1.0.3 Class A

101

* ESP32 PICO D4

102

* SX1276/78 Wireless Chip

103

* Arduino IDE Compatible

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

* Datalog

== 1.4 Applications ==

117

118

119

* Logistics and Supply Chain Management

* Human tracking

= 2. Use TrackerD =

== 2.1 How it works? ==

126

127

128

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.

129

130

131

== 2.2 Quick guide to connect to LoRaWAN server ==

132

133

134

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.

135

136

137

[[image:1664501652064-326.png||_mstalt="293306"]]

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:

142

143

144

(% style="color:blue" %)**Step 1**:(%%) Create a device in TTN V3 with the OTAA keys from TrackerD.

145

146

Each TrackerD is shipped with a sticker with the default device EUI as below:

147

148

149

[[image:1664501677253-891.png||_mstalt="296569"]]

150

151

152

Input these keys to their LoRaWAN Server portal. Below is TTN V3 screen shot:

153

154

155

**__Add APP EUI in the application:__**

156

157

158

[[image:1664501711466-918.png||_mstalt="295828"]]

[[image:1664501721248-725.png||_mstalt="294450"]]

163

164

165

[[image:1664501734705-405.png||_mstalt="293306"]]

**__Add APP KEY and DEV EUI:__**

170

171

172

[[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"]]

(% style="color:blue" %)**Step 2**:(%%) Push this button will activate this device.

177

178

(% id="cke_bm_7709S" style="display:none" %) [[image:1664502835802-546.png||_mstalt="295061"]]

179

180

[[image:1664502835802-546.png||_mstalt="295061"]]

181

182

183

(% 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.

184

185

186

== 2.3 Positioning Mode(SMOD) ==

187

188

189

Users can set TrackerD to different Positioning Mode for different applications. Below mod are supported.

190

191

* (% style="color:#037691" %)**GPS ONLY(Factory Settings): **(%%)Only get and uplink GPS location info.

192

* (% 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.

193

* (% 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.

194

195

Users can switch modes by [[changing SMOD>>||anchor="H3.2.7SetPositioningMode"]].

196

197

198

== 2.4 Uplink Payload ==

199

200

=== 2.4.1 Uplink FPORT~=5, Device Status ===

201

202

203

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.

204

205

Use can also get the Device Status uplink through the downlink command: **Downlink: 0x2301**

206

207

208

(% border="1.5" style="background-color:#ffffcc; color:green; width:440px" %)

[[image:1665301570342-765.png||_mstalt="294580"]]

213

214

215

(% style="color:#037691" %)**Example of Device Status:**(%%) 13014001FF0FA24002

216

217

(% style="color:#037691" %)**Sensor Model:** (%%) For TrackerD,this value is 0x13

218

219

(% style="color:#037691" %)**Firmware Version: **(%%) 0x0140,Means:v1.4.0 version

220

221

(% style="color:#037691" %)**Frequency Band**:

*0x01: EU868

*0x02: US915

*0x03: IN865

*0x04: AU915

*0x05: KZ865

*0x06: RU864

*0x07: AS923

*0x08: AS923-1

*0x09: AS923-2

*0x0a: AS923-3

Sub- Band:value 0x00~~0x08(only forAU915,US915,Others are 0xFF)

244

245

(% style="color:#037691" %)**BAT:**(%%) shows the battery voltage for TrackerD.

246

247

248

(% style="color:#037691" %)**Ex1:**(%%) 0x0FA2 = 4002mV

249

250

Use can also get the Device Status uplink through the downlink command:

251

252

253

(% style="color:#037691" %)**SMOD Field (total 1 byte)**(%%)：0x40

254

255

(% border="1.5" style="background-color:#ffffcc; color:green; width:270px" %)

256

|=(% scope="row" style="width: 60px;" %)**Size(bit)**|(% style="width:50px" %)2bits|(% style="width:80px" %)2bit|(% style="width:80px" %)4bit

257

|=(% style="width: 75px;" %)**Value**|(% style="width:64px" %)SMOD|(% style="width:104px" %)GPS_Settings|(% style="width:103px" %)BLE_Settings

258

259

(% style="color:blue" %)** SMOD：**

260

261

(% style="color:red" %)** 1 :** (%%) GPS ONLY

262

263

(% style="color:red" %)** 2 :** (%%) BLE ONLY

264

265

(% style="color:red" %)** 3 :** (%%) GPS/BLE Hybrid

266

267

268

(% style="color:blue" %)** GPS_MOD: Define how to send GPS payload**

269

270

(% style="color:red" %)** 0 : ** (%%) Enable uploading on-board Temperature and humidity values

271

272

(% style="color:red" %)** 1 :** (%%) Disable uploading on-board Temperature and humidity values

273

274

275

(% style="color:blue" %)** BLE_Settings:**

276

277

(% style="color:red" %)** 1: ** (%%) BLE Positioning with Strongest iBeacon

278

279

(% _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)(%%)

280

281

282

(% style="color:#037691" %)**Status Field (total 1 byte)**(%%): 0x02

283

284

(% border="1.5" style="background-color:#ffffcc; color:green; width:260px" %)

285

286

|=(% 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"]]

287

288

289

=== 2.4.2 Uplink FPORT~=2, Realtime GNSS Positioning + Temperature & Humidity ===

290

291

292

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,

293

294

295

(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:320px" %)

296

|=(% scope="row" style="width: 60px;" %)(((

**Size(bytes)**

2

)))|(% style="width:30px" %)(((

301

2

302

)))

303

|=(% style="width: 69px;" %)**Value**|(% style="width:76px" %)[[Latitude>>||anchor="HLocationinfo:"]]|(% style="width:87px" %)[[Longitude>>||anchor="HLocationinfo:"]]|(% style="width:76px" %)(((

304

[[Alarm & BAT>>||anchor="HAlarm26BAT:"]]

305

)))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]]|(% style="width:40px" %)[[Hum>>||anchor="HHum:"]]|(% style="width:87px" %)[[Tem>>||anchor="HTem:"]]

306

307

[[image:1665301636888-168.png||_mstalt="298012"]]

308

309

310

==== (% style="color:blue" %)**Alarm & BAT:**(%%) ====

311

312

(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:250px" %)

313

|=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:50px" %)1 bit|(% style="width:80px" %)1bit|(% style="width:50px" %)14bits

314

|=(% style="width: 72px;" %)**Value**|(% style="width:67px" %)reserve|(% style="width:118px" %)Alarm Indicate|(% style="width:63px" %)[[BAT>>||anchor="HBAT:"]]

315

316

==== (% style="color:blue" %)**FLAG:**(%%) ====

317

318

(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:120px" %)

319

|=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:30px" %)2bits|(% style="width:30px" %)1bit

320

|=(% style="width: 79px;" %)**Value**|(% style="width:55px" %)[[MOD>>||anchor="H3.2.7SetPositioningMode"]]|(% style="width:47px" %)[[LON>>||anchor="HLON:"]]

321

322

**Example:** Payload: 0x02863D68 FAC29BAF 4B45 60 0202 011A

323

324

325

==== (% style="color:blue" %)**Location info:**(%%) ====

326

327

* Latitude: 02863D68 ⇒ //if (0x//02863D68//& 0x80000000 = 0 )~:// //value = 02863D68 /1000000 = 42.351976//

328

* Longitude: FAC29BAF ⇒ //if (0x//FAC29BAF// & 0x80000000 = 1 )~:// //value = (0x//FAC29BAF// – 0x 100000000)/1000000 =//-87.9094//57//

329

330

(% style="color:red" %)**Important note:**

331

332

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.

333

334

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:

335

336

337

[[image:1664502116362-706.png||_mstalt="293306"]]

338

339

340

3. While GPS can't get location info after timeout(FTIME Parameter), the latitude and longitude will be filled with all 0x00:

341

342

[[image:1664502166010-515.png||_mstalt="291395"]]

==== (% style="color:blue" %)**Alarm:**(%%) ====

347

348

**Example: ** 0x4B & 0x40 >> 6 = 0x01

349

350

351

==== (% style="color:blue" %)**BAT:**(%%) ====

352

353

**Example: ** 0x4B45 & 0x3FFF ⇒ 2885 (mV).

354

355

(((

356

The battery info shows the battery voltage, User can use the below mapping to indicate the battery in percentage: \

357

)))

358

359

* > 4.0v : 80% ~~ 100%

360

* 3.85v ~~3.99v: 60% ~~ 80%

361

* 3.70v ~~ 3.84v: 40% ~~ 60%

362

* 3.40v ~~ 3.69v: 20% ~~ 40%

* < 3.39v: 0~~20%

==== (% style="color:blue" %)**MOD:**(%%) ====

367

368

**Example: ** (0x60>>6) & 0x3f =1

369

370

**Set the format of GPS data uplink link：**

371

372

(% style="color:#037691" %)**0x00:** (%%) Enable uploading on-board Temperature and humidity values

373

(% style="color:#037691" %)**0x01: ** (%%) Disable uploading on-board Temperature and humidity values

374

375

376

**Set the format of BLE data uplink link：**

377

378

(% style="color:#037691" %)**0x01: ** (%%) BLE Positioning with Strongest iBeacon

379

380

381

==== (% style="color:blue" %)**LON:**(%%) ====

382

383

**Example:** (0x60>>5) & 0x01=1.

384

385

Enable/Disable LED activity for uplink

386

387

(((

388

(% style="color:#037691" %)**0x00:** (%%) Disable LED indicator.

)))

(((

(% style="color:#037691" %)**0x01:** (%%) Enable LED indicator (Default Value)

)))

==== (% style="color:blue" %)**Hum:**(%%) ====

397

398

0202 = //if (0x0202 & 0x8000 = 0 ): value =// 0x0202 / 100 = +514 ⇒ 51.4 degree

399

400

401

==== (% style="color:blue" %)**Tem:**(%%) ====

402

403

011A =if (0x011A & 0x8000 = 1 ): value =( 0x011A - 0x10000)/10(dec) ⇒ -//28.2 degree//

404

405

406

=== 2.4.3 Uplink FPORT~=3, Realtime GNSS Positioning (Default Mode) ===

407

408

409

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)

410

411

412

(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:300px" %)

413

|=(% scope="row" style="width: 60px;" %)(((

414

**Size(bytes)**

415

)))|(% style="width:60px" %)4|(% style="width:60px" %)4|(% style="width:60px" %)2|(% style="width:50px" %)1

416

|=(% style="width: 69px;" %)**Value**|(% style="width:76px" %)[[Latitude>>||anchor="HLocationinfo:"]]|(% style="width:87px" %)[[Longitude>>||anchor="HLocationinfo:"]]|(% style="width:76px" %)(((

417

[[Alarm & BAT>>||anchor="HAlarm26BAT:"]]

418

)))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]]

419

420

(% class="wikigeneratedid" %)

421

[[image:1665301687277-443.png||_mstalt="296140"]]

422

423

424

=== 2.4.4 Uplink FPORT~=4, History GNSS Positioning ===

425

426

427

Set [[PNACKMD=1>>||anchor="H3.2.11A0AutoSendNone-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.

428

429

430

(% style="color:red" %)**Note for this mode:**

431

432

* a) TrackerD will do an ACK check for data records sending to make sure every data arrive server.

433

* 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.

434

* 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

435

436

The payload is 15 bytes, as below.

437

438

(% border="1.5" style="background-color:#ffffcc; color:green; width:500px" %)

439

|=(% scope="row" %)(((

**Size(bytes)**

)))|4|4|2|1|1|1|1|1

[[image:image-20221009160309-2.png||_mstalt="429312"]]

445

446

447

=== 2.4.5 Uplink FPORT~=6, BLE Positioning with Strongest iBeacon ===

448

449

450

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.

451

452

User can set **[[BLEMASK>>||anchor="H3.2.11A0SetBLEMASKtofilterBLEiBeacon"]]** so TrackerD will only search the iBeacons which have UUID that match the BLEMASK settings.

453

454

455

(% border="1.5" cellspacing="3" style="background-color:#ffffcc; color:green; width:450px" %)

456

|=(% scope="row" style="width: 60px;" %)(((

457

**Size(bytes)**

458

459

|=(% style="width: 50px;" %)**Value**|(% style="width:44px" %)[[UUID>>||anchor="HLocationinfo:"]]|(% style="width:61px" %)(((

460

iBeacon MAJOR

461

)))|(% style="width:63px" %)(((

462

iBeacon MINOR

463

)))|(% style="width:71px" %)(((

464

iBeacon Measured Power

465

)))|(% style="width:50px" %)(((

466

iBeacon RSSI

467

)))|(% style="width:47px" %)(((

468

[[Alarm & BAT>>||anchor="HAlarm26BAT:"]]

469

)))|(% style="width:15px" %)[[FLAG>>||anchor="HFLAG:"]]

470

471

[[image:1664502425687-834.png||_mstalt="296738"]]

472

473

474

* (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV).

475

* (% style="color:#037691" %)**MODE: **(%%)Define the payload format.

476

* (% style="color:#037691" %)**UUID: **(%%)The uuid from the strongest iBeacon.

477

* (% style="color:#037691" %)**MAJOR:** (%%) The MAJOR from the strongest iBeacon.

478

* (% style="color:#037691" %)**MINOR:** (%%)The MINOR from the strongest iBeacon.

479

* (% style="color:#037691" %)**Measured Power: ** (%%) The Measured Power from the strongest iBeacon.

480

* (% style="color:#037691" %)**RSSI: ** (%%) The RSSI from the strongest iBeacon.

481

482

483

=== 2.4.6 Uplink FPORT~=8, WiFi Positioning with Strongest WiFi SSID（Since firmware 1.4.1） ===

484

485

486

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.

487

488

489

(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:371.222px" %)

490

|=(% scope="row" style="width: 60px;" %)(((

491

**Size(bytes)**

492

)))|(% style="width:60px" %)6|(% style="width:60px" %)4|(% style="width:79px" %)2|(% style="width:66px" %)1

493

|=(% style="width: 69px;" %)**Value**|(% style="width:76px" %)SSID|(% style="width:87px" %)RSSI|(% style="width:79px" %)(((

494

[[Alarm & BAT>>||anchor="HAlarm26BAT:"]]

495

)))|(% style="width:66px" %)[[FLAG>>||anchor="HFLAG:"]]

496

497

(% class="wikigeneratedid" %)

498

[[image:1667288597595-714.png||_mstalt="299598" height="212" width="1151"]]

499

500

501

* (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV).

502

* (% style="color:#037691" %)**SSID: **(%%)WiFi name.

503

* (% style="color:#037691" %)**RSSI: **(%%)The RSSI from the strongest WiFi.

504

505

506

=== 2.4.7 Add Payload format in TTN V3 ===

507

508

509

In TTN V3, user can add a custom payload so it shows friendly.

510

511

In the page (% style="color:#037691" %)**Applications ~-~-> Payload Formats ~-~-> Custom ~-~-> decoder**

512

513

514

[[image:1664502649601-895.png||_mstalt="296985"]]

Add the decoder from this link:

519

520

[[https:~~/~~/github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD>>https://github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD]]

521

522

Save the change the uplink message will be parsed. As below:

523

524

[[image:1664502676891-606.png||_mstalt="296673"]]

525

526

527

== 2.5 Integrate with Datacake ==

528

529

530

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.

531

532

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]]

533

534

535

[[image:1664502695771-538.png||_mstalt="297349"]]

536

537

538

== 2.6 Integrate with Tago ==

539

540

541

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.

542

543

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]]

544

545

546

[[image:1664502715371-321.png||_mstalt="292162"]]

547

548

549

== 2.7 Datalog Feature ==

550

551

552

total 273 entries,by default,

553

554

User can set [[PNACKMD=1>>||anchor="H3.2.11A0AutoSendNone-ACKmessages"]], to enable Datalog feature.

Example use case.

[[image:image-20221009234703-2.png||_mstalt="429143" height="328" width="899"]]

559

560

561

[[image:image-20221009234629-1.png||_mstalt="431145" height="390" width="577"]]

== 2.8 Alarm Mode ==

(((

User can push the (% style="color:red" %)**RED button**(%%) by more than 5 seconds to enter Alarm Mode.

)))

(((

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.

)))

(((

**Two ways to exit alarm mode:**

579

)))

580

581

* Server sends a downlink command to exit.

582

* User fast press the RED button 10 times.

583

584

(((

585

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.

)))

== 2.9 Transport Mode ==

590

591

592

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.

593

594

* **[[MTDC>>||anchor="H3.2.3SetTransportModePackettransmissioninterval"]]** defines the Uplink Interval during transportation.

595

* **[[TDC>>||anchor="H3.2.1SetTransmitInterval"]]** defines the uplink interval when TrackerD is stactic.

596

* **[[PT>>||anchor="H3.2.16GetorSetThresholdformotiondetectFF08Sincefirmware1.4.3FF09"]]** defines the threldhold to detect a motion.

597

598

599

== 2.10 LED Status ==

600

601

602

(% border="1.5" style="background-color:#ffffcc; width:500px" %)

603

|=(% style="width: 150px;" %)**Event**|=(% style="width: 200px;" %)**Action**|=(% style="width: 150px;" %)**AT+LON to control on/off**

604

|(% 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

605

|(% style="width:157px" %)**Join request**|(% style="width:271px" %)(% style="color:green" %)**Green** (%%)led fast blink once (200ms)|(% style="width:202px" %)Yes

606

|(% style="width:157px" %)**Join Success**|(% style="width:271px" %)(% style="color:green" %)**Green**(%%) led on 5 second|(% style="width:202px" %)N/A

607

|(% style="width:157px" %)**Fixing Location**|(% style="width:271px" %)(% style="color:blue" %)**BLUE **(%%)blinks 200ms per second|(% style="width:202px" %)Yes

608

|(% style="width:157px" %)**Fixed and uplink**|(% style="width:271px" %)(% style="color:green" %)**GREEN **(%%)blinks twice (200ms per blink)|(% style="width:202px" %)Yes

609

|(% style="width:157px" %)**Fail Fix and uplink**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)blinks twice (200ms per blink)|(% style="width:202px" %)Yes

610

|(% style="width:157px" %)**Enter Alarm mode**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)on for 3 seconds|(% style="width:202px" %)Yes

611

|(% style="width:157px" %)**Uplink under Alarm**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)on for 1 second|(% style="width:202px" %)Yes

612

|(% style="width:157px" %)**Exit Alarm**|(% style="width:271px" %)(% style="color:blue" %)**BLUE **(%%)led on 5 second|(% style="width:202px" %)Yes

613

|(% style="width:157px" %)**Get Downlink**|(% style="width:271px" %)(% style="color:green" %)**GREEN**(%%) led on 1 second|(% style="width:202px" %)Yes

614

|(% style="width:157px" %)**Movement Detect**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)led on 500ms|(% style="width:202px" %)N/A

615

616

617

== 2.11 Button Function ==

618

619

620

(% style="color:blue" %)**RESET button:**

621

622

[[image:1664502835802-546.png||_mstalt="295061"]]

623

624

Push this button will reboot the device. Device will exit alarm mode and re-join to LoRaWAN server.

625

626

627

(% style="color:red" %)**RED button:**

628

629

[[image:1664502854406-763.png||_mstalt="295568"]]

630

631

632

(% border="1" style="background-color:#ffffcc; width:510px" %)

633

|=(% style="width: 100px;" %)**Function**|=(% style="width: 205px;" %)**Action**|=(% style="width: 205px;" %)**Description**

634

|(% 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"]]

635

|(% 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

636

|(% 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.

637

638

639

== 2.12 USB Port Function ==

640

641

642

The USB interface of TrackerD has below functions:

643

644

* Power on the device

645

* Recharge the battery

646

* [[Configure Device>>||anchor="H3.ConfigureTrackerDviaATcommandorLoRaWANdownlink"]]

647

* [[Upgrade Firmware>>||anchor="H5.UploadFirmware"]]

648

649

650

= 3. Configure TrackerD via AT command or LoRaWAN downlink =

651

652

653

User can configure TrackerD via AT Command or LoRaWAN Downlink.

654

655

LoRaWAN Downlink instruction for different platforms: [[IoT LoRaWAN Server>>doc:Main.WebHome]]

656

657

658

== 3.1 Access AT Command ==

659

660

661

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.

662

663

664

[[image:1664502999401-486.png||_mstalt="296985"]]

665

666

667

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:

668

669

670

[[image:1664503022490-662.png||_mstalt="293332"]]

671

672

673

[[image:1664503035713-500.png||_mstalt="291096"]]

674

675

676

[[image:1664503047675-651.png||_mstalt="295386"]]

677

678

679

== 3.2 Command Set ==

680

681

=== 3.2.1 Set Transmit Interval ===

682

683

684

Set device uplink interval.

685

686

* (% style="color:blue" %)**AT Command:**

687

688

(% style="color:#037691" %)**AT+TDC=xxx **

689

690

Example: AT+TDC=300000. Means set interval to 5 minutes(300 seconds)

691

692

693

* (% style="color:blue" %)**Downlink Payload (prefix 0x01):**

694

695

(% style="color:#037691" %)**0x01 00 01 2C** (%%) ~/~/ Same as AT+TDC=300000

696

697

698

=== 3.2.2 Set Alarm Packet transmission interval ===

699

700

701

Set alarm packet transmit interval

702

703

* (% style="color:blue" %)**AT Command:**

704

705

(% style="color:#037691" %)**AT+ATDC=xx. **

706

707

Example: AT+ATDC=60000 **~-~-> ** Set Alarm Packet Interval to 60 seconds. TrackerD will send every 60 seconds in Alarm mode, Default Value: 60000

708

709

710

* (% style="color:blue" %)**Downlink Payload (prefix 0xB1):**

711

712

(% style="color:#037691" %)**0xB1 00 00 3C ** (%%) ~/~/ Same as AT+ATDC=60000

713

714

715

=== 3.2.3 Set Transport Mode Packet transmission interval ===

716

717

718

Set Transport Mode packet transmit interval

719

720

* (% style="color:blue" %)**AT Command:**

721

722

(% style="color:#037691" %)**AT+MTDC=xx. **

723

724

Example: AT+MTDC=300000 **~-~-> ** Set Transport Mode Packet Interval to 300 seconds. TrackerD will send every 300 seconds in Transport mode, Default Value: 300000

725

726

727

* (% style="color:blue" %)**Downlink Payload (prefix 0x03):**

728

729

(% style="color:#037691" %)**0x03 00 01 2C** (%%) ~/~/ Same as AT+MTDC=3000000

730

731

732

=== 3.2.4 Exit Alarm ===

733

734

735

Server send downlink command to exit Alarm mode

736

737

* (% style="color:blue" %)**AT Command: No AT Command**

738

739

* (% style="color:blue" %)**Downlink Payload (prefix 0x02):**

740

741

(% style="color:#037691" %)**0x02 01** (%%) ~/~/ Exit Alarm Mode

742

743

744

=== 3.2.5 Disable/Enable LED flash ===

745

746

747

Disable/Enable LED for position, downlink and uplink

748

749

* (% style="color:blue" %)**AT Command:**

750

751

(% style="color:#037691" %)**AT+LON=xx. (Disable (0), Enable (1), default:1)**

752

753

Example: AT+LON=0 **~-~-> ** Disable LED for position, downlink and uplink.

754

755

756

* (% style="color:blue" %)**Downlink Payload (prefix 0xAE):**

757

758

(% style="color:#037691" %)**0xAE 00 ** (%%) ~/~/ Same as AT+LON=0

759

760

761

=== 3.2.6 Disable/Enable Transport Mode ===

762

763

764

Users can use this feature to enable/disable Transport Mode.

765

766

* (% style="color:blue" %)**AT Command:**

767

768

(% style="color:#037691" %)**AT+INTWK=xx. (Disable (0), Enable (1), default:0)**

769

770

Example: AT+INTWK=1 **~-~-> ** Enable Transport Mode.

771

772

773

* (% style="color:blue" %)**Downlink Payload (prefix 0xAF):**

774

775

(% style="color:#037691" %)**0xAF 01 ** (%%) ~/~/ Same as AT+INTWK=1

776

777

778

=== 3.2.7 Set Positioning Mode ===

779

780

781

SMOD define how TrackerD scan and uplink data:

782

783

784

* (% style="color:blue" %)**AT Command:**

785

786

(% style="color:#037691" %)**AT+SMOD=aa,bb,cc**

787

788

(% style="color:#037691" %)** aa:**

789

790

* (% style="color:red" %)**1: GPS ONLY(Factory Settings): **(%%)Only get and uplink GPS location info.

791

792

* (% 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.

793

794

* (% 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.

795

796

(% style="color:#037691" %)**bb:**

797

798

* (% style="color:red" %)**0 : **(%%)GPS+ BAT+ State+Tem&Hum

799

800

* (% style="color:red" %)**1 :**(%%) GPS +BAT State

801

802

(% style="color:#037691" %)**cc: **

803

804

* (% _mstmutation="1" style="color:red" %)**1 : **(%%) (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State

805

806

* (% _mstmutation="1" style="color:red" %)**2 : **(%%) (WiFi)SSID+Rssi+BAT+State ((% _mstmutation="1" style="color:#037691" %)V1.4.1 Version support this function later(%%))

807

808

(% style="color:blue" %)**Example:**

809

810

AT+SMOD=1,0,0 ~-~-> GPS+ BAT+ State+Tem&Hum

811

812

AT+SMOD=1,1,0 ~-~-> GPS +BAT State

813

814

AT+SMOD=2,0,1 ~-~-> (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State

815

816

AT+SMOD=2,0,2 ~-~-> (WiFi)SSID+Rssi+BAT+State

817

818

819

* (% style="color:blue" %)**Downlink Payload (prefix 0xA5):**

820

821

(% style="color:#037691" %)**0xA5 01 00 00** (%%) ~/~/ Same as AT+SMOD=1,0,0

822

823

824

=== 3.2.8 Set MAX GPS position time ===

825

826

827

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.

828

829

830

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.

831

832

833

* (% style="color:blue" %)**AT Command:**

834

835

(% style="color:#037691" %)**AT+FTIME=xx** (%%) **~-~-> ** Set to use xx as max fix time.

836

837

**Example:** AT+FTIME=150

838

839

840

* (% style="color:blue" %)**Downlink Payload (prefix 0xAA):**

841

842

(% style="color:#037691" %)**0xAA 00 96 ** (%%) ~/~/ Set AT+FTIME=150

843

844

845

=== 3.2.9 Set PDOP value for GPS fix accuracy ===

846

847

848

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.

849

850

851

A GPS packet with lower PDOP has higher accuracy. PDOP default value is 2.0

852

853

854

* (% style="color:blue" %)**AT Command:**

855

856

(% style="color:#037691" %)**AT+PDOP=2.5 ** (%%) **~-~-> ** Set PDOP to 2.5

857

858

859

* (% style="color:blue" %)**Downlink Payload (prefix 0xAD):**

860

861

(% style="color:#037691" %)**0xAD 00 0A** (%%) ~/~/ Set AT+PDOP=1 (0x0A / 10 =1)

862

863

(% style="color:#037691" %)**0xAD 00 19** (%%) ~/~/ Set AT+PDOP=2.5 (0x19 / 10 =2.5)

864

865

(% style="color:#037691" %)**0xAD 00 46** (%%) ~/~/ Set AT+PDOP=7 (0x46 / 10 =7)

866

867

868

=== 3.2.10 Disable/Enable the confirmation mode ===

869

870

871

* (% style="color:blue" %)**AT Command:**

872

873

(% style="color:#037691" %)**AT+CFM=xx**

**~ Example:**

AT+CFM=0 **~-~-> ** Disable confirmation

879

880

AT+CFM=1 **~-~-> ** Enable confirmation

881

882

883

* (% style="color:blue" %)**Downlink Payload (prefix 0x05):**

884

885

(% style="color:#037691" %)**0x05 01 **(%%) ~/~/ Same as AT+CFM=1

886

887

888

=== 3.2.11 Auto Send None-ACK messages ===

889

890

891

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.

892

893

894

* (% style="color:blue" %)**AT Command: AT+PNACKMD**

895

896

The default factory setting is 0.

897

898

899

**Command Example Function Response:**

900

901

(% style="color:#037691" %)**AT+PNACKMD=1** (%%) ~/~/ Poll None-ACK message OK

902

903

904

* (% style="color:blue" %)**Downlink Command: 0x34**

905

906

Example: 0x34 01 ~/~/ Same as AT+PNACKMD=1

907

908

909

=== 3.2.12 Set BLEMASK to filter BLE iBeacon ===

910

911

912

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.

913

914

(% style="color:red" %)**Note: BLEMASK range is 6 ~~ 10 bytes. If AT+BLEMASK < 6 bytes, BLEMASK will be disabled.**

915

916

(% style="color:blue" %)**AT Command:**

917

918

(% _mstmutation="1" style="color:#037691" %)**AT+BLEMASK=123456** (%%) ~/~/ Set BLEMASK = 123456

919

920

(% _mstmutation="1" style="color:#037691" %)**AT+BLEMASK=0** (%%) ~/~/ disable BLEMASK

921

922

(% style="color:blue" %)**Downlink Payload: (Prefix : 0xB2)(Since firmware 1.4.1）**

923

924

Example: 0xB2 01 02 03 04 05 06 ~/~/ Set BLEMASK to 123456

925

926

927

=== 3.2.13 Set WiFIMASK to filter WiFi SSID（Since firmware 1.4.1） ===

928

929

930

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.

931

932

(% style="color:red" %)**Note: WiFiMASK range is 6 ~~ 10 bytes. If AT+ WiFiMASK < 6 bytes, WiFiMASK will be disabled.**

933

934

(% style="color:blue" %)**AT Command:**

935

936

(% _mstmutation="1" style="color:#037691" %)**AT+WiFiMASK=123456** (%%) ~/~/ Set WiFiMASK = 123456

937

938

(% _mstmutation="1" style="color:#037691" %)**AT+WiFiMASK=0** (%%) ~/~/ disable WiFiMASK

939

940

(% style="color:blue" %)**Downlink Payload: (Prefix : 0xB3)(Since firmware 1.4.1）**

941

942

Example: 0xB3 01 02 03 04 05 06 ~/~/ Set WiFiMASK to 123456

943

944

945

=== 3.2.14 Disable/Enable Information printing（Since firmware 1.4.1） ===

946

947

948

Users can use this feature to enable/disable Information printing.

949

950

(% style="color:blue" %)**AT Command:**

951

952

(% style="color:#037691" %)**AT+SHOWID=XX **(%%) ~/~/ (Disable (0), Enable (1), default:0)

953

\\Example: AT+SHOWID=1 ~-~-> Enable Information printing.

954

955

956

=== 3.2.15 Get or Set Eight Channels Mode, only for us915, AU915（Since firmware 1.4.1） ===

957

958

959

The Channels Mode in the LORAWAN LMIC library is from 0 ~~ 7. When CHE = 8, 72 channels will be accessible to the network.

960

961

(% style="color:blue" %)**AT Command:**

962

963

(% style="color:#037691" %)**AT+CHE=1 **(%%) ~/~/ set one channels mode

964

965

966

(% style="color:blue" %)**Downlink Payload:0X24**

967

968

Example: 0x24 01 ~/~/ Same as AT+CHE=1

969

970

971

=== 3.2.16 Get or Set Threshold for motion detect（Since firmware 1.4.3） ===

972

973

974

User can set the motion detect thredhold for transportation mode. The smaller the value, the more sensitivity to trigger a motion event.

975

976

(% style="color:blue" %)**AT Command:**

977

978

(% style="color:#037691" %)**AT+PT=xx**

Example:

AT+PT=14 ~-~-> Set to detect car motion.

983

984

AT+PT=41 ~-~-> set to detect walk motion.

985

986

987

(% style="color:blue" %)**Downlink Payload:0xB4**(%%)

988

0xB4 14 ~/~/ Same as AT+PT=14

989

990

991

= 4. Setting for Different Scenarios =

= 5. Upload Firmware =

996

997

== 5.1 Firmware Change Log ==

998

999

1000

**[[See this link>>url:https://github.com/dragino/TrackerD]]**

1001

1002

1003

== 5.2 How to upgrade firmware ==

1004

1005

1006

User can use the TrackerD's USB port to upgrade firmware into it. The hardware connection for upgrade firmware is as below:

1007

1008

1009

(% style="color:blue" %)**Step1: **(%%)Connect TrackerD and PC via USB cable shipped with TrackerD.

1010

1011

1012

(% style="color:blue" %)**Step2:** (%%) Install CH9102 driver in the PC.

1013

1014

After installation of the driver and plug in TrackerD, user should be able to see com port in PC's device manager.

1015

1016

1017

(% 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]]

1018

1019

1020

(% style="color:blue" %)**Step4:** (%%) Run Flash Download Tool and configure chip type to ESP32

1021

1022

1023

[[image:1664503563660-578.png||_mstalt="296777"]]

1024

1025

1026

[[image:1664503574618-659.png||_mstalt="297986"]]

(% style="color:blue" %)**Step5:** (%%) Select the firmware file (.bin format), com port and proper SPI configure. Clink Start. Bin file location:

1031

1032

[[https:~~/~~/github.com/dragino/TrackerD/releases>>https://github.com/dragino/TrackerD/releases]]

1033

1034

1035

**Users need to use below files:**

boot_app0.bin @0e000

US915.bin @ 0x10000(Select the bin file of the frequency band you need)

1040

1041

1042

[[image:image-20221207120501-1.png]]

After upgrade finish, it will show finish as below:

1047

1048

[[image:image-20221207133911-7.png]]

1049

1050

1051

= 6. Developer Guide =

1052

1053

== 6.1 Compile Source Code ==

1054

1055

=== 6.1.1 Set up ARDUINO compile environment ===

1056

1057

1058

* **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]]**

1059

1060

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]]

1061

1062

1063

[[image:1664503635019-941.png||_mstalt="294658"]]

* (% style="color:#037691" %)**Go to tools ~-~-> Boards ~-~-> Boards Manager**,(%%) **find the esp32 information and install it.**

1068

1069

[[image:1664503715811-892.png||_mstalt="295698"]]

1070

1071

1072

=== 6.1.2 Build the development environment ===

1073

1074

~1. Download and install arduino IDE

1075

1076

[[https:~~/~~/www.arduino.cn/thread-5838-1-1.html>>url:https://links.jianshu.com/go?to=https%3A%2F%2Fwww.arduino.cn%2Fthread-5838-1-1.html]]

1077

1078

1079

2. Download the ESP32 development package in the arduino IDE

1080

1081

[[image:image-20221213100007-1.png]]

1082

1083

Input: [[https:~~/~~/dl.espressif.com/dl/package_esp32_index.json>>https://dl.espressif.com/dl/package_esp32_index.json]]

1084

1085

[[image:image-20221213100626-2.png]]

1086

1087

Restart the IDE after the addition is complete, then:

1088

1089

[[image:image-20221213100808-3.png||height="679" width="649"]]

1090

1091

[[image:image-20221213101040-4.png]]

1092

1093

**Note: Currently version 1.04 is almost impossible to download, you can choose version 1.03.

1094

Don't quit halfway.~~! If you quit halfway, there is a high probability that it will freeze, and you will need to download again next time. (If you click to continue downloading, an error will be reported after completion)**

1095

1096

Then enter a long waiting process. If you don't want to wait, you can go to the Internet to download directly, and then import:

1097

1098

Methods as below:

1099

~1. Download: https:~/~/pan.baidu.com/s/1kU6jlbh

1100

1101

2. Find the arduino installation path, hardware → create a new espressif folder → create a new esp32 folder, unzip the compressed package here.

1102

1103

(% 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.

1104

1105

[[image:image-20221213102311-5.png||height="582" width="711"]]

1106

1107

3. Find tools→get.exe in the decompressed file and run it (it will close automatically after completion)

1108

1109

[[image:image-20221213102334-6.png]]

1110

1111

**Note: This step requires a python environment**

1112

1113

Either way, in the end:

1114

The final effect is to open the arduino and you can see the esp32

1115

1116

[[image:image-20221213102718-7.png||height="1053" width="803"]]

[[image:image-20221024105643-1.png||_mstalt="428129"]]

**~ Figure1**

[[image:image-20221024105643-2.png||_mstalt="428493"]]

**Figure2**

* **Download the latest TrackerD from the dragino github: [[https:~~/~~/github.com/dragino/TrackerD>>url:https://github.com/dragino/TrackerD]]**

1132

1133

Put the Library in the TrackerD directory into the libraries file in the Arduino directory:

1134

1135

1136

[[image:1664503752288-974.png||_mstalt="298194"]]

1137

1138

1139

== 6.2 Source Code ==

1140

1141

1142

* (% style="color:blue" %)**Open the example in the TrackerD file, please select the correct port in the IDE, as shown below:**

1143

1144

[[image:1664503794261-827.png||_mstalt="296387"]]

* (% style="color:blue" %)**Click to upload**

1149

1150

[[image:1664503808294-336.png||_mstalt="295711"]]

* (% style="color:blue" %)**Check the result, if the upload is successful, as shown below, open the serial port to view the data**

1155

1156

[[image:1664503824081-592.png||_mstalt="294918"]] [[image:1664503831430-500.png||_mstalt="290784"]]

= 7. FAQ =

== 7.1 How to change the LoRa Frequency Bands/Region? ==

1162

1163

1164

User can follow the introduction for [[how to upgrade image>>||anchor="H5.UploadFirmware"]]. When download the images, choose the required image file for download.

1165

1166

1167

== 7.2 What is the pin mapping for the USB program cable? ==

1168

1169

1170

[[image:1664499635206-262.png||_mstalt="295360"]]

(% border="1.5" cellspacing="3" style="background-color:#ffffcc; color:green; width:314px" %)

1175

|=(% style="width: 118px;" %)**Pin**|=(% style="width: 67px;" %)**Color**|=(% style="width: 123px;" %)**USB Pin**

1176

|(% style="width:118px" %)A4,B4,A9,B9|(% style="width:67px" %)Red|(% style="width:123px" %)VCC

1177

|(% style="width:118px" %)A7,B7|(% style="width:67px" %)White|(% style="width:123px" %)D- (N/A)

1178

|(% style="width:118px" %)A6,B6|(% style="width:67px" %)Green|(% style="width:123px" %)D+(N/A)

1179

|(% style="width:118px" %)A1,B1,A12,B12|(% style="width:67px" %)Black|(% style="width:123px" %)GND

1180

|(% style="width:118px" %)A5|(% style="width:67px" %)Purple|(% style="width:123px" %)MTDC/GOIO13

1181

|(% style="width:118px" %)B5|(% style="width:67px" %)Blue|(% style="width:123px" %)MTDC/GPIO12

1182

|(% style="width:118px" %)A8|(% style="width:67px" %)Yellow|(% style="width:123px" %)MTMS/GPIO14

1183

|(% style="width:118px" %)B8|(% style="width:67px" %)Grey|(% style="width:123px" %)MTDO/GPIO15

1184

1185

1186

== 7.3 Notes on using different serial port tools for TrackerD ==

1187

1188

=== 7.3.1 Serial port utility ===

1189

1190

1191

Serial port utility requires you to automatically add data streams.

1192

1193

Need to adjust the data stream to RTS/CTS on physical restart.

1194

1195

(% class="wikigeneratedid" %)

1196

[[image:image-20221102140621-1.png||_mstalt="425672"]]

When using AT commands, the data flow needs to be adjusted to XON/XOFF

1201

1202

[[image:image-20221102140638-2.png||_mstalt="428727"]]

1203

1204

1205

=== 7.3.2 SecureCRT ===

1206

1207

1208

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.

1209

1210

1211

[[image:image-20221102140704-3.png||_mstalt="427076"]]

1212

1213

1214

[[image:image-20221102140712-4.png||_mstalt="427089"]]

=== 7.3.3 PUTTY ===

[[image:image-20221102140748-5.png||_mstalt="430456"]]

1221

1222

1223

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.

1224

1225

1226

[[image:image-20221102140801-6.png||_mstalt="427466"]]

1227

1228

1229

== 7.4 How to modify source code to compile different frequency band bin file? ==

1230

1231

1232

(% class="box infomessage" %)

1233

(((

1234

(% style="color:red" %)**Important**(%%): Developer **MUST** follow the Arduino Environment Instruction exactly include change the SPI pin mappings.

1235

See : [[**Set Up Arduino Compile Environment for TrackerD**. >>||anchor="H6.1.1SetupARDUINOcompileenvironment"]]

1236

)))

1237

1238

**~1. When compiling the frequency band, you need to find LMIC_PROJECT_CONFIG.H file.**

1239

1240

1241

[[image:image-20221116111844-1.png||_mstalt="428688" height="227" width="782"]]

**2. Open LMIC_PROJECT_CONFIG.H, find the corresponding macro definition and open it(AS923_2,AS923_3,AS923_4 except).**

1246

1247

1248

[[image:image-20221116111844-2.png||_mstalt="429052" height="262" width="781"]]

**3. Compile the AS923_JP band, please refer to the intention shown**

1253

1254

1255

[[image:image-20221116111844-3.png||_mstalt="429416" height="338" width="746"]]

**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.**

1260

1261

1262

[[image:image-20221116111844-4.png||_mstalt="429780" height="641" width="739"]]

1263

1264

1265

[[image:image-20221116111844-5.png||_mstalt="430144" height="551" width="708"]]

1266

1267

1268

= 8 Trouble Shooting =

1269

1270

== 8.1 TDC is changed to 4294947296 and cause no uplink. ==

(((

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

)))

== 8.2 Device not able get AT Command or show output after wake up from deep sleep mode ==

(((

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.

)))

== 8.3 Problem after Upgrading Firmware ==

1287

1288

=== 8.3.1 "rst: (0x3 SW_RESET)" and Continue Restart after upgrading ===

**Error Output**

[[image:image-20221122100004-4.png||_mstalt="424606"]]

(((

Some partition is missed during upgrade, please upgrade below four files as example:

1299

1300

[[image:image-20221207120524-2.png]]

)))

=== 8.3.2 TrackerD's led light is always GREEN on after upgrading ===

1305

1306

1307

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

1308

1309

1310

=== 8.3.3 "flash read err" after upgrade firmware ===

1311

1312

1313

Error shows below, user might erase the entire flash include u-boot partition which cause this issue.

1314

1315

1316

[[image:image-20221122100004-1.png||_mstalt="423514" height="497" width="534"]]

1317

1318

1319

User need to upgrade again with below four files to solve this issue.

1320

1321

[[image:image-20221207120530-3.png]]

**Figure 2**

=== 8.3.4 "Device Key become ff ff ff ff ff ff ff ff " after upgrade firmware ===

1327

1328

1329

User might erase the entire flash include keys and default settings which cause this issue.

1330

1331

After the upgrade is completed, enter **AT+CFG** as shown in the figure below.

1332

1333

1334

[[image:image-20221122100004-3.png||_mstalt="424242"]]

1335

1336

1337

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.

1338

1339

After AT+FDR. please set

1340

1341

* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=7**

1342

1343

* (% _mstmutation="1" style="color:blue" %)**AT+FTIME=180000**

**Example:**

AT+PDOP=7.00

AT+FTIME=180

AT+DEUI=70B3D57ED0053981

1352

1353

AT+APPEUI=D23345667BCBCCAF

1354

1355

AT+APPKEY=F402A1A7A350445A7CD2DEA95511BFA1

1356

1357

AT+DADDR=260b4dce ( no need for OTAA)

1358

1359

AT+NWKSKEY=71cb7672441f573a53d4f34d307fc61d ( no need for OTAA)

1360

1361

AT+APPSKEY=dacce2299ecd97a73ee3f80b5a46a559 ( no need for OTAA)

1362

1363

1364

== 8.4 When positioning, it will restart or the PDOP setting is unsuccessful ==

1365

1366

1367

Please download version 1.4.2 again

1368

1369

1370

== 8.5 How to deal with unsuccessful GPS positioning? ==

1371

1372

1373

1） Make Sure the device is in Open Area where can see the sky.

1374

1375

2) Set PDOP to a higher value.

1376

1377

* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=2 **(%%)(can be positioned precisely.）

1378

1379

* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=7 **(%%)(Quickly locate in open spaces）

1380

1381

* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=14.7** (%%)(Positioning can be acquired in complex environments）

1382

1383

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

1384

1385

1386

== 8.6 When upgrading the firmware, the data is not completely erased, and the information does not return to normal after multiple resets ==

1387

1388

1389

When upgrading, use the erase button to upgrade

1390

1391

[[image:image-20221207120536-4.png]]

1392

1393

1394

The parameters are displayed abnormally and cannot be fixed using AT+FDR

1395

1396

[[image:image-20221128103040-2.png||height="431" width="525"]]

1397

1398

1399

Please upgrade these four files,link（The boot_app0 file is in the version folder you need)

1400

1401

[[image:image-20221207134028-8.png]]

1402

1403

1404

Reboot information after upgrade

1405

1406

[[image:image-20221128111443-4.png||height="432" width="546"]]

1407

1408

1409

Use AT+FDR command to reset and then use AT+CFG to check whether the configuration is back to normal

1410

1411

[[image:image-20221128111850-5.png]]

1412

1413

1414

After the parameters return to normal, upgrade to the version you need again

1415

1416

[[image:image-20221207120601-5.png]]

1417

1418

1419

At this point, the parameters return to normal after running AT+FDR again

1420

1421

[[image:image-20221128112035-7.png]]

= 9. Order Info =

Part Number: (% style="color:blue" %)**TrackerD-XXX**

1428

1429

(% style="color:blue" %)**XXX**(%%): The default frequency band

1430

1431

* (% style="color:red" %)**EU433**(%%): Default frequency band EU433

1432

1433

* (% style="color:red" %)**EU868**(%%): Default frequency band EU868

1434

1435

* (% style="color:red" %)**IN865**(%%): Default frequency band IN865

1436

1437

* (% style="color:red" %)**KR920**(%%): Default frequency band KR920

1438

1439

* (% style="color:red" %)**AS923**(%%): Default frequency band AS923

1440

1441

* (% style="color:red" %)**AU915**(%%): Default frequency band AU915

1442

1443

* (% style="color:red" %)**US915**(%%): Default frequency band US915

= 10. Packing Info =

(% style="color:#037691" %)**Package Includes**:

1450

1451

* TrackerD LoRaWAN GPS/BLE Tracker x 1

1452

1453

* USB recharge & program cable x 1

1454

1455

(% style="color:#037691" %)**Dimensions and Weight**:

1456

1457

* Device Size: 85 x 48 x 15 mm

* Weight: 50g

= 11. Support =

* 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.

1466

1467

* 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]].

= 12. Reference =

* [[**Firmware in Bin format**>>https://www.dropbox.com/sh/733s8xlwahhqg1d/AABxDz80lBVX_to8zNuUQWFja?dl=0]]

1474

1475

* **[[Source Code>>https://github.com/dragino/TrackerD]] **

1476