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

22

)))

23

24

(((

25

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

26

27

(((

28

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.

)))

[[image:1664499921684-770.png]]

43

44

45

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

46

47

48

== 1.2 Specifications ==

49

50

51

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

52

53

* Espressif ESP32 PICO D4

54

* MCU: ESP32 PICO D4

55

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

56

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

57

* Integrated SPI flash : 4 MB

* RAM: 448 KB

* EEPROM: 520 KB

* Clock Speed: 32Mhz

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

63

64

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

65

* Operating Temperature: -40 ~~ 60°C

66

67

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

68

69

* Frequency Range,

70

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

71

* 168 dB maximum link budget.

72

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

73

* +14 dBm high efficiency PA.

74

* Programmable bit rate up to 300 kbps.

75

* High sensitivity: down to -148 dBm.

76

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

77

* Excellent blocking immunity.

78

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

79

* Fully integrated synthesizer with a resolution of 61 Hz.

80

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

81

* Built-in bit synchronizer for clock recovery.

82

* Preamble detection.

83

* 127 dB Dynamic Range RSSI.

84

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

85

* Packet engine up to 256 bytes with CRC.

86

* LoRaWAN 1.0.3 Specification

87

88

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

89

90

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

91

92

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

93

94

* Sleeping Mode: 200uA

95

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

96

* Tracking: max: 38mA

== 1.3 Features ==

* LoRaWAN 1.0.3 Class A

102

* ESP32 PICO D4

103

* SX1276/78 Wireless Chip

104

* Arduino IDE Compatible

105

* Open source hardware / software

106

* Regular/ Real-time GPS,BLE,WIFI tracking

107

* Built-in3 axis accelerometer (LIS3DH)

108

* Humidity / temperature sensor : GXCAS Technology GXHT3X

109

* Motion sensing capability

110

* Power Monitoring

111

* Charging circuit via USB port

112

* 1000mA Li-on Battery power

113

* Tri-color LED, Alarm button

114

* Datalog

115

116

== 1.4 Applications ==

117

118

119

* Logistics and Supply Chain Management

* Human tracking

= 2. Use TrackerD =

== 2.1 How it works? ==

125

126

127

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.

128

129

130

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

131

132

133

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.

134

135

136

[[image:1664501652064-326.png]]

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:

141

142

143

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

144

145

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

146

147

148

[[image:1664501677253-891.png]]

149

150

151

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

152

153

154

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

155

156

157

[[image:1664501711466-918.png]]

[[image:1664501721248-725.png]]

162

163

164

[[image:1664501734705-405.png]]

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

169

170

171

[[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||alt="1654671889112-678.png"]]

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

176

177

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

178

179

[[image:1664502835802-546.png]]

180

181

182

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

183

184

185

== 2.3 Positioning Mode(SMOD) ==

186

187

188

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

189

190

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

191

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

192

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

193

194

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

195

196

197

== 2.4 Uplink Payload ==

198

199

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

200

201

202

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.

203

204

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

205

206

207

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

[[image:1665301570342-765.png]]

212

213

214

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

215

216

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

217

218

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

219

220

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

243

244

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

245

246

247

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

248

249

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

250

251

252

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

253

254

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

255

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

256

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

257

258

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

259

260

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

261

262

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

263

264

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

265

266

267

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

268

269

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

270

271

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

272

273

274

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

275

276

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

277

278

(% style="color:red" %)** 2：** (%%)WiFi Positioning with Strongest WiFi SSID(% style="color:blue" %)(V1.4.1 Version support this function later)(%%)

279

280

281

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

282

283

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

284

285

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

286

287

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

288

289

290

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,

291

292

293

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

294

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

**Size(bytes)**

2

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

299

2

300

)))

301

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

302

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

303

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

304

305

[[image:1665301636888-168.png]]

306

307

308

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

309

310

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

311

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

312

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

313

314

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

315

316

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

317

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

318

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

319

320

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

321

322

323

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

324

325

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

326

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

327

328

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

329

330

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.

331

332

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:

333

334

335

[[image:1664502116362-706.png]]

336

337

338

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

339

340

[[image:1664502166010-515.png]]

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

345

346

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

347

348

349

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

350

351

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

352

353

(((

354

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

355

)))

356

357

* > 4.0v : 80% ~~ 100%

358

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

359

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

360

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

361

* < 3.39v: 0~~20%

362

363

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

364

365

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

366

367

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

368

369

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

370

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

371

372

373

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

374

375

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

376

377

378

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

379

380

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

381

382

Enable/Disable LED activity for uplink

383

384

(((

385

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

)))

(((

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

)))

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

394

395

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

396

397

398

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

399

400

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

401

402

403

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

404

405

406

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)

407

408

409

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

410

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

411

**Size(bytes)**

412

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

413

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

414

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

415

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

416

417

(% class="wikigeneratedid" %)

418

[[image:1665301687277-443.png]]

419

420

421

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

422

423

424

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

425

426

427

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

428

429

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

430

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

431

* 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

432

433

The payload is 15 bytes, as below.

434

435

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

436

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

**Size(bytes)**

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

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

442

443

444

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

445

446

447

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.

448

449

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

450

451

452

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

453

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

454

**Size(bytes)**

455

456

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

457

iBeacon MAJOR

458

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

459

iBeacon MINOR

460

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

461

iBeacon Measured Power

462

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

463

iBeacon RSSI

464

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

465

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

466

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

467

468

[[image:1664502425687-834.png]]

469

470

471

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

472

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

473

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

474

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

475

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

476

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

477

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

478

479

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

480

481

482

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.

483

484

485

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

486

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

487

**Size(bytes)**

488

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

489

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

490

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

491

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

492

493

(% class="wikigeneratedid" %)

494

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

495

496

497

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

498

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

499

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

500

501

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

502

503

504

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

505

506

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

507

508

509

[[image:1664502649601-895.png]]

Add the decoder from this link:

514

515

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

516

517

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

518

519

[[image:1664502676891-606.png]]

520

521

522

== 2.5 Integrate with Datacake ==

523

524

525

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.

526

527

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

528

529

530

[[image:1664502695771-538.png]]

531

532

533

== 2.6 Integrate with Tago ==

534

535

536

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.

537

538

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

539

540

541

[[image:1664502715371-321.png]]

542

543

544

== 2.7 Datalog Feature ==

545

546

547

total 273 entries,by default,

548

549

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

Example use case.

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

554

555

556

[[image:image-20221009234629-1.png||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:**

574

)))

575

576

* Server sends a downlink command to exit.

577

* User fast press the RED button 10 times.

578

579

(((

580

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

585

586

587

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.

588

589

590

== 2.10 LED Status ==

591

592

593

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

594

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

595

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

596

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

597

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

598

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

599

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

600

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

601

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

602

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

603

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

604

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

605

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

606

607

== 2.11 Button Function ==

608

609

610

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

611

612

[[image:1664502835802-546.png]]

613

614

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

615

616

617

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

618

619

[[image:1664502854406-763.png]]

620

621

622

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

623

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

624

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

625

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

626

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

627

628

== 2.12 USB Port Function ==

629

630

631

The USB interface of TrackerD has below functions:

632

633

* Power on the device

634

* Recharge the battery

635

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

636

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

637

638

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

639

640

641

User can configure TrackerD via AT Command or LoRaWAN Downlink.

642

643

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

644

645

646

== 3.1 Access AT Command ==

647

648

649

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.

650

651

652

[[image:1664502999401-486.png]]

653

654

655

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:

656

657

658

[[image:1664503022490-662.png]]

659

660

661

[[image:1664503035713-500.png]]

662

663

664

[[image:1664503047675-651.png]]

== 3.2 Command Set ==

669

670

=== 3.2.1 Set Transmit Interval ===

671

672

673

Set device uplink interval.

674

675

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

676

677

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

678

679

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

680

681

682

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

683

684

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

685

686

687

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

688

689

690

Set alarm packet transmit interval

691

692

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

693

694

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

695

696

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

697

698

699

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

700

701

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

702

703

704

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

705

706

707

Set Transport Mode packet transmit interval

708

709

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

710

711

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

712

713

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

714

715

716

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

717

718

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

719

720

721

=== 3.2.4 Exit Alarm ===

722

723

724

Server send downlink command to exit Alarm mode

725

726

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

727

728

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

729

730

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

731

732

733

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

734

735

736

Disable/Enable LED for position, downlink and uplink

737

738

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

739

740

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

741

742

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

743

744

745

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

746

747

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

748

749

750

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

751

752

753

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

754

755

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

756

757

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

758

759

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

760

761

762

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

763

764

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

765

766

767

=== 3.2.7 Set Positioning Mode ===

768

769

770

SMOD define how TrackerD scan and uplink data:

771

772

773

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

774

775

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

776

777

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

778

779

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

780

781

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

782

783

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

784

785

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

786

787

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

788

789

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

790

791

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

792

793

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

794

795

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

796

797

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

798

799

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

800

801

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

802

803

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

804

805

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

806

807

808

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

809

810

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

811

812

813

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

814

815

816

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.

817

818

819

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.

820

821

822

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

823

824

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

825

826

**Example:** AT+FTIME=150

827

828

829

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

830

831

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

832

833

834

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

835

836

837

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.

838

839

840

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

841

842

843

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

844

845

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

846

847

848

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

849

850

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

851

852

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

853

854

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

**Disable/Enable the confirmation mode**

859

860

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

861

862

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

**~ Example:**

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

868

869

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

870

871

872

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

873

874

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

875

876

877

=== 3.2.10 Auto Send None-ACK messages ===

878

879

880

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.

881

882

883

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

884

885

The default factory setting is 0.

886

887

888

**Command Example Function Response:**

889

890

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

891

892

893

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

894

895

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

896

897

898

=== 3.2.11 Set BLEMASK to filter BLE iBeacon ===

899

900

901

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.

902

903

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

904

905

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

906

907

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

908

909

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

910

911

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

912

913

Example: 0xB2010203040506 ~/~/ Set BLEMASK to 123456

914

915

916

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

917

918

919

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.

920

921

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

922

923

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

924

925

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

926

927

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

928

929

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

930

931

Example: 0xB3010203040506 ~/~/ Set WiFiMASK to 123456

932

933

934

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

935

936

937

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

938

939

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

940

941

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

942

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

943

944

945

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

946

947

948

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

949

950

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

951

952

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

953

954

955

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

956

957

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

958

959

960

= 4. Setting for Different Scenarios =

= 5. Upload Firmware =

965

966

== 5.1 Firmware Change Log ==

967

968

969

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

970

971

972

== 5.2 How to upgrade firmware ==

973

974

975

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

976

977

978

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

979

980

981

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

982

983

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

984

985

986

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

987

988

989

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

990

991

992

[[image:1664503563660-578.png]]

993

994

995

[[image:1664503574618-659.png]]

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

1000

1001

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

1002

1003

1004

**Users need to use below files:**

boot_app0.bin @0e000

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

1009

1010

1011

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

After upgrade finish, it will show finish as below:

1016

1017

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

= 6. Developer Guide =

1022

1023

== 6.1 Compile Source Code ==

1024

1025

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

1026

1027

1028

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

1029

1030

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

1031

1032

1033

[[image:1664503635019-941.png]]

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

1038

1039

[[image:1664503715811-892.png]]

1040

1041

1042

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

1043

1044

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

**~ Figure1**

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

**Figure2**

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

1055

1056

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

1057

1058

1059

[[image:1664503752288-974.png]]

1060

1061

1062

== 6.2 Source Code ==

1063

1064

1065

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

1066

1067

[[image:1664503794261-827.png]]

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

1072

1073

[[image:1664503808294-336.png]]

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

1078

1079

[[image:1664503824081-592.png]] [[image:1664503831430-500.png]]

= 7. FAQ =

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

1085

1086

1087

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

1088

1089

1090

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

1091

1092

1093

[[image:1664499635206-262.png]]

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

1098

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

1099

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

1100

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

1101

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

1102

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

1103

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

1104

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

1105

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

1106

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

1107

1108

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

1109

1110

=== 7.3.1 Serial port utility ===

1111

1112

1113

Serial port utility requires you to automatically add data streams.

1114

1115

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

1116

1117

(% class="wikigeneratedid" %)

1118

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

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

1123

1124

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

1125

1126

1127

=== 7.3.2 SecureCRT ===

1128

1129

1130

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.

1131

1132

1133

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

1134

1135

1136

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

=== 7.3.3 PUTTY ===

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

1143

1144

1145

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.

1146

1147

1148

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

1149

1150

1151

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

1152

1153

1154

(% class="box infomessage" %)

1155

(((

1156

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

1157

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

1158

)))

1159

1160

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

1161

1162

1163

[[image:image-20221116111844-1.png||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).**

1168

1169

1170

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

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

1175

1176

1177

[[image:image-20221116111844-3.png||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.**

1182

1183

1184

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

1185

1186

1187

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

1188

1189

1190

= 8 Trouble Shooting =

1191

1192

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

(((

Before firmware v1.4.0: When the Transport Mode is enabled (**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 ==

1209

1210

=== 8.3.1 Continue Restart after upgrading ===

(((

If it is V1.4.0 and the previous version, new partitions need to be loaded when upgrading. The new version of the software is stored in the partition package. The upgrade method is shown in the figure

)))

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

1219

1220

1221

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

1222

1223

1224

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

1225

1226

1227

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

1228

1229

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

1230

1231

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

1232

1233

1234

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

1235

1236

[[image:image-20221122100004-2.png||height="619" width="389"]]

**Figure 2**

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

1242

1243

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

1244

1245

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

1246

1247

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

1248

1249

Please **AT+FDR** which will reset all settings to factory settings. , and then input the following keys by the information on the label.

Example:

AT+DEUI=70B3D57ED0053981

1255

1256

AT+APPEUI=D23345667BCBCCAF

1257

1258

AT+APPKEY=F402A1A7A350445A7CD2DEA95511BFA1

1259

1260

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

1261

1262

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

1263

1264

AT+APPSKEY=dacce2299ecd97a73ee3f80b5a46a559 ( no need for OTAA)

=== 8.3.4 If there is a situation in Figure 1, and a new partition file needs to be added. Please refer to the operation steps in chapter 8.3.1 ===

1269

1270

1271

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

1272

1273

1274

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

1275

1276

1277

Please download version 1.4.2 again

1278

1279

1280

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

1281

1282

1283

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

1284

1285

2) Set PDOP to a higher value.

1286

1287

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

1288

1289

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

1290

1291

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

1292

1293

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

= 9. Order Info =

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

1300

1301

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

1302

1303

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

1304

1305

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

1306

1307

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

1308

1309

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

1310

1311

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

1312

1313

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

1314

1315

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

= 10. Packing Info =

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

1321

1322

* TrackerD LoRaWAN GPS/BLE Tracker x 1

1323

1324

* USB recharge & program cable x 1

1325

1326

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

1327

1328

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

1336

1337

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

1343

1344

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

1345

1346

* [[**Hardware Source**>>https://www.dropbox.com/sh/orwoy6cecb89m4e/AAD37sRuUrvKsHgAJxuVTkB5a?dl=0]]

Wiki source code of TrackerD -LoRaWAN Tracker User Manual

Applications

Navigation