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:image-20230213110119-1.png||height="382" width="834"]]

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:image-20230213110214-2.png||height="388" width="847"]]

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" %)1bits|(% 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:412.222px" %)

285

286

|=(% style="width: 75px;" %)**Value**|(% style="width:68px" %)Reserve|(% style="width:87px" %)[[PNACKMD>>||anchor="H2.4.4A0UplinkFPORT3D42CHistoryGNSSPositioning"]]|(% style="width:49px" %)[[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:279.222px" %)

313

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

314

|=(% style="width: 72px;" %)**Value**|(% style="width:67px" %)reserve|(% style="width:69px" %)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:183.222px" %)

319

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

320

|=(% style="width: 79px;" %)**Value**|(% style="width:55px" %)[[MOD>>||anchor="H3.2.7SetPositioningMode"]]|(% style="width:52px" %)[[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%

363

* < 3.39v: 0~~20%

364

365

(% style="display:none" %) (%%)

366

367

368

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

369

370

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

371

372

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

373

374

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

375

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

376

377

378

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

379

380

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

381

382

383

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

384

385

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

386

387

Enable/Disable LED activity for uplink

388

389

(((

390

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

)))

(((

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

)))

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

399

400

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

401

402

403

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

404

405

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

406

407

408

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

409

410

411

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)

412

413

414

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

415

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

416

**Size(bytes)**

417

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

418

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

419

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

420

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

421

422

(% class="wikigeneratedid" %)

423

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

424

425

426

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

427

428

429

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.

430

431

432

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

433

434

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

435

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

436

* 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

437

438

The payload is 15 bytes, as below.

439

440

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

441

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

**Size(bytes)**

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

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

447

448

449

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

450

451

452

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.

453

454

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

455

456

457

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

458

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

459

**Size(bytes)**

460

461

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

462

iBeacon MAJOR

463

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

464

iBeacon MINOR

465

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

466

iBeacon Measured Power

467

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

468

iBeacon RSSI

469

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

470

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

471

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

472

473

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

474

475

476

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

477

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

478

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

479

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

480

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

481

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

482

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

483

484

(% style="display:none" %) (%%)

485

486

487

=== 2.4.6 Uplink FPORT~=7, Alarm information status（Since firmware 1.4.4） ===

488

489

490

The upward link device is configured to FPORT = 7. Once Trackerd alarm, it will upload the news to the server.

491

492

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

493

|**Size(bytes)**|2|1

494

|**Value**|[[Alarm & BAT>>path:#HAlarm26BAT:]]|Mod+lon

495

496

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

497

498

alarm=(bytes[0] & 0x40) ~/~/ Alarm status

499

500

batV=~(~(~(bytes[0] & 0x3f) <<8) | bytes[1])/1000; ~/~/ Battery,units:V

501

502

mod = bytes[2] & 0xC0;

503

504

Lon=(bytes[2] & 0x20)

505

506

507

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

508

509

510

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.

511

512

513

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

514

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

515

**Size(bytes)**

516

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

517

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

518

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

519

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

520

521

(% class="wikigeneratedid" %)

522

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

523

524

525

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

526

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

527

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

528

529

(% style="display:none" %) (%%)

530

531

532

=== 2.4.8 Add Payload format in TTN V3 ===

533

534

535

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

536

537

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

538

539

540

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

Add the decoder from this link:

545

546

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

547

548

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

549

550

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

551

552

553

== 2.5 Integrate with Datacake ==

554

555

556

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.

557

558

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

559

560

561

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

562

563

564

== 2.6 Integrate with Tago ==

565

566

567

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.

568

569

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

570

571

572

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

573

574

575

== 2.7 Integrate with Node-red ==

576

577

~1. Install node-red, please refer to the installation method in the link:

578

579

[[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Node-RED/#H1.A0Installation>>http://wiki.dragino.com/xwiki/bin/view/Main/Node-RED/#H1.A0Installation]]

580

2. Import the created flow template, please refer to the import method in the link:

581

582

[[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Node-RED/#H3.A0Importsampleflow>>http://wiki.dragino.com/xwiki/bin/view/Main/Node-RED/#H3.A0Importsampleflow]]

583

The address of the flow template:

584

585

[[dragino-end-node-decoder/TrackerD.json at main · dragino/dragino-end-node-decoder · GitHub>>url:https://github.com/dragino/dragino-end-node-decoder/blob/main/Node-RED/TrackerD.json]]

586

587

Note: If you are using NODE-RED for the first time, please search and install the two plug-ins in the figure below in node-red to fully use the flow template

588

589

[[image:image-20230307135914-1.png||height="527" width="1045"]]

590

591

[[image:image-20230307135932-2.png||height="527" width="1044"]]

592

593

(% class="wikigeneratedid" %)

594

== ==

595

596

== 2.8 Datalog Feature ==

597

598

599

total 273 entries,by default,

600

601

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

606

607

608

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

== 2.9 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:**

626

)))

627

628

* Server sends a downlink command to exit.

629

* User fast press the RED button 10 times.

630

631

(((

632

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.10 Transport Mode ==

637

638

639

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.

640

641

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

642

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

643

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

644

645

(% style="display:none" %) (%%)

646

647

648

== 2.11 LED Status ==

649

650

651

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

652

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

653

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

654

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

655

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

656

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

657

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

658

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

659

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

660

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

661

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

662

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

663

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

664

665

(% style="display:none" %) (%%)

666

667

668

== 2.12 Button Function ==

669

670

671

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

672

673

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

674

675

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

676

677

678

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

679

680

[[image:image-20230213110506-3.png]](% style="display:none" %)

681

682

(% style="display:none" %) (%%)

683

684

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

685

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

686

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

687

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

688

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

689

690

(% style="display:none" %) (%%)

691

692

693

== 2.13 USB Port Function ==

694

695

696

The USB interface of TrackerD has below functions:

697

698

* Power on the device

699

* Recharge the battery

700

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

701

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

702

703

(% style="display:none" %) (%%)

704

705

706

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

707

708

709

User can configure TrackerD via AT Command or LoRaWAN Downlink.

710

711

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

712

713

714

== 3.1 Access AT Command ==

715

716

717

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.

718

719

720

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

721

722

723

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:

724

725

726

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

727

728

729

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

730

731

732

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

733

734

(% style="display:none" %) (%%)

735

736

== 3.2 Command Set ==

737

738

=== 3.2.1 Set Transmit Interval ===

739

740

741

Set device uplink interval.

742

743

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

744

745

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

746

747

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

748

749

750

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

751

752

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

753

754

755

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

756

757

758

Set alarm packet transmit interval

759

760

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

761

762

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

763

764

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

765

766

767

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

768

769

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

770

771

772

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

773

774

775

Set Transport Mode packet transmit interval

776

777

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

778

779

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

780

781

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

782

783

784

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

785

786

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

787

788

789

=== 3.2.4 Exit Alarm ===

790

791

792

Server send downlink command to exit Alarm mode

793

794

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

795

796

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

797

798

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

799

800

801

=== 3.2.5 Disable/Enable LED flash and buzzer ===

802

803

804

Disable/Enable LED for position, downlink and uplink

805

806

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

807

808

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

809

810

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

811

812

813

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

814

815

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

816

817

818

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

819

820

821

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

822

823

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

824

825

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

826

827

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

828

829

830

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

831

832

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

833

834

835

=== 3.2.7 Set Positioning Mode ===

836

837

838

SMOD define how TrackerD scan and uplink data:

839

840

841

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

842

843

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

844

845

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

846

847

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

848

849

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

850

851

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

852

853

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

854

855

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

856

857

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

858

859

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

860

861

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

862

863

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

864

865

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

866

867

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

868

869

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

870

871

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

872

873

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

874

875

876

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

877

878

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

879

880

881

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

882

883

884

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.

885

886

887

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.

888

889

890

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

891

892

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

893

894

**Example:** AT+FTIME=150

895

896

897

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

898

899

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

900

901

902

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

903

904

905

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.

906

907

908

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

909

910

911

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

912

913

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

914

915

916

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

917

918

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

919

920

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

921

922

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

923

924

925

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

926

927

928

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

929

930

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

**~ Example:**

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

936

937

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

938

939

940

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

941

942

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

943

944

945

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

946

947

948

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.

949

950

951

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

952

953

The default factory setting is 0.

954

955

956

**Command Example Function Response:**

957

958

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

959

960

961

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

962

963

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

964

965

966

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

967

968

969

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.

970

971

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

972

973

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

974

975

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

976

977

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

978

979

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

980

981

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

982

983

984

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

985

986

987

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.

988

989

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

990

991

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

992

993

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

994

995

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

996

997

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

998

999

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

1000

1001

1002

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

1003

1004

1005

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

1006

1007

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

1008

1009

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

1010

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

1011

1012

1013

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

1014

1015

1016

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

1017

1018

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

1019

1020

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

1021

1022

1023

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

1024

1025

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

1026

1027

1028

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

1029

1030

1031

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

1032

1033

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

1034

1035

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

Example:

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

1040

1041

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

1042

1043

1044

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

1045

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

1046

1047

1048

= 4. Setting for Different Scenarios =

= 5. Upload Firmware =

1053

1054

== 5.1 Firmware Change Log ==

1055

1056

1057

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

1058

1059

1060

== 5.2 How to upgrade firmware ==

1061

1062

1063

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

1064

1065

1066

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

1067

1068

1069

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

1070

1071

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

1072

1073

1074

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

1075

1076

1077

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

1078

1079

1080

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

1081

1082

1083

[[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:

1088

1089

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

1090

1091

1092

**Users need to use below files:**

boot_app0.bin @0e000

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

1097

1098

1099

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

After upgrade finish, it will show finish as below:

1104

1105

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

1106

1107

1108

= 6. Developer Guide =

1109

1110

== 6.1 Compile Source Code ==

1111

1112

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

1113

1114

1115

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

1116

1117

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

1118

1119

1120

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

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

1125

1126

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

1127

1128

1129

=== 6.1.2 Build the development environment ===

1130

1131

1132

**~1. Download and install arduino IDE**

1133

1134

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

1135

1136

1137

**2. Download the ESP32 development package in the arduino IDE**

1138

1139

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

1140

1141

1142

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

1143

1144

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

1145

1146

1147

Restart the IDE after the addition is complete, then:

1148

1149

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

1150

1151

1152

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

1153

1154

1155

(% style="color:red" %)**Note: Currently version 1.04 is almost impossible to download, you can choose version 1.03.

1156

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

1157

1158

1159

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:

1160

1161

(% style="color:blue" %)**Methods as below:**

1162

1163

~1. Download: [[https:~~/~~/github.com/dragino/TrackerD/releases/tag/v1.4.4>>https://github.com/dragino/TrackerD/releases/tag/v1.4.4]]

1164

1165

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

1166

1167

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

1168

1169

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

1170

1171

1172

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

1173

1174

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

1175

1176

(% style="color:red" %)**Note: This step requires a python environment**

1177

1178

1179

Either way, in the end:

1180

1181

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

1182

1183

[[image:image-20221213110952-8.png||height="866" width="711"]]

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

1199

1200

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

1201

1202

1203

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

1204

1205

1206

== 6.2 Source Code ==

1207

1208

1209

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

1210

1211

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

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

1216

1217

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

1222

1223

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

= 7. FAQ =

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

1229

1230

1231

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

1232

1233

1234

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

1235

1236

1237

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

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

1242

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

1243

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

1244

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

1245

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

1246

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

1247

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

1248

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

1249

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

1250

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

1251

1252

(% style="display:none" %) (%%)

1253

1254

1255

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

1256

1257

=== 7.3.1 Serial port utility ===

1258

1259

1260

Serial port utility requires you to automatically add data streams.

1261

1262

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

1263

1264

(% class="wikigeneratedid" %)

1265

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

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

1270

1271

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

1272

1273

1274

=== 7.3.2 SecureCRT ===

1275

1276

1277

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.

1278

1279

1280

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

1281

1282

1283

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

=== 7.3.3 PUTTY ===

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

1290

1291

1292

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.

1293

1294

1295

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

1296

1297

1298

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

1299

1300

1301

(% class="box infomessage" %)

1302

(((

1303

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

1304

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

1305

)))

1306

1307

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

1308

1309

1310

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

1315

1316

1317

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

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

1322

1323

1324

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

1329

1330

1331

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

1332

1333

1334

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

1335

1336

1337

== 7.5 Are there example python example for BLE Indoor Positioning? ==

1338

1339

1340

[[Operating instructions for BLE indoor positioning>>doc:.Example of BLE indoor positioning python.WebHome]]

1341

1342

1343

= 8 Trouble Shooting =

1344

1345

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

1362

1363

=== 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:

1374

1375

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

)))

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

1380

1381

1382

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

1383

1384

1385

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

1386

1387

1388

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

1389

1390

1391

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

1392

1393

1394

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

1395

1396

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

**Figure 2**

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

1402

1403

1404

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

1405

1406

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

1407

1408

1409

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

1410

1411

1412

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.

1413

1414

After AT+FDR. please set

1415

1416

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

1417

1418

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

**Example:**

AT+PDOP=7.00

AT+FTIME=180

AT+DEUI=70B3D57ED0053981

1427

1428

AT+APPEUI=D23345667BCBCCAF

1429

1430

AT+APPKEY=F402A1A7A350445A7CD2DEA95511BFA1

1431

1432

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

1433

1434

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

1435

1436

AT+APPSKEY=dacce2299ecd97a73ee3f80b5a46a559 ( no need for OTAA)

1437

1438

1439

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

1440

1441

1442

Please download version 1.4.2 again

1443

1444

1445

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

1446

1447

1448

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

1449

1450

2) Set PDOP to a higher value.

1451

1452

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

1453

1454

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

1455

1456

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

1457

1458

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

1459

1460

1461

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

1462

1463

1464

When upgrading, use the erase button to upgrade

1465

1466

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

1467

1468

1469

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

1470

1471

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

1472

1473

1474

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

1475

1476

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

1477

1478

1479

Reboot information after upgrade

1480

1481

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

1482

1483

1484

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

1485

1486

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

1487

1488

1489

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

1490

1491

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

1492

1493

1494

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

1495

1496

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

1497

1498

1499

== 8.7 If you encounter the following problems, please upgrade to the latest version ==

1500

1501

1502

~1. Press and hold the red button (more than 5 seconds), and the device and server do not respond.

1503

1504

2. Send some commands through the serial port to prompt an error (Example：AT+SMOD=1,0,1)

= 9. Order Info =

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

1511

1512

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

1513

1514

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

1515

1516

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

1517

1518

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

1519

1520

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

1521

1522

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

1523

1524

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

1525

1526

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

1527

1528

(% style="display:none" %) (%%)

= 10. Packing Info =

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

1535

1536

* TrackerD LoRaWAN GPS/BLE Tracker x 1

1537

1538

* USB recharge & program cable x 1

1539

1540

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

1541

1542

* Device Size: 85 x 48 x 15 mm

* Weight: 50g

(% style="display:none" %) (%%)

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

1553

1554

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

1555

1556

(% style="display:none" %) (%%)

= 12. Reference =

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

1563