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

103

* ESP32 PICO D4

104

* SX1276/78 Wireless Chip

105

* Arduino IDE Compatible

106

* Open source hardware / software

107

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

108

* Built-in3 axis accelerometer (LIS3DH)

109

* Humidity / temperature sensor : GXCAS Technology GXHT3X

110

* Motion sensing capability

111

* Power Monitoring

112

* Charging circuit via USB port

113

* 1000mA Li-on Battery power

114

* Tri-color LED, Alarm button

* Datalog

== 1.4 Applications ==

119

120

121

* Logistics and Supply Chain Management

* Human tracking

= 2. Use TrackerD =

== 2.1 How it works? ==

128

129

130

TrackerD is configured as LoRaWAN OTAA Class A GPS tracker by default. It has OTAA keys to join LoRaWAN network. To connect a LoRaWAN network, user need to input the OTAA keys in the LoRaWAN IoT server and push reset button of TrackerD (next to USB port). TrackerD will wake up and auto join the network via OTAA.

131

132

133

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

134

135

136

Here is an example for how to join the [[TTNv3 LoRaWAN Network>>url:https://eu1.cloud.thethings.network]]. Below is the network structure, we use LPS8N as LoRaWAN gateway in this example.

137

138

139

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

144

145

146

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

147

148

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

149

150

151

[[image:1664501677253-891.png]]

152

153

154

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

155

156

157

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

158

159

160

[[image:1664501711466-918.png]]

[[image:1664501721248-725.png]]

165

166

167

[[image:1664501734705-405.png]]

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

172

173

174

[[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LDS02%20-%20LoRaWAN%20Door%20Sensor%20User%20Manual/WebHome/1654671889112-678.png?rev=1.1||alt="1654671889112-678.png"]]

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

179

180

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

181

182

[[image:1664502835802-546.png]]

183

184

185

(% style="color:blue" %)**Step 3:**(%%) TrackerD will auto join to the LoRaWAN network. After join success, TrackerD will start to upload message to IoT server.

186

187

188

== 2.3 Positioning Mode(SMOD) ==

189

190

191

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

192

193

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

194

* (% style="color:#037691" %)**BLE or WiFi ONLY: **(%%)** **Only obtain iBeacon info via BLE and uplink or obtain wifi ssid info via WiFi and uplink. Design for Indoor tracking.

195

* (% style="color:#037691" %)**GPS/BLE Hybrid: **(%%)Combination for Indoor and Outdoor tracking. Devices will try to search BLE iBeacon first. If device can't find the iBeacon, it will use GPS for positioning.

196

197

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

198

199

200

== 2.4 Uplink Payload ==

201

202

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

203

204

205

Uplink the device configures with FPORT=5. Once TrackerD Joined the network, it will uplink this message to the server. After the first uplink, TrackerD will uplink Device Status every 12 hours.

206

207

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

208

209

210

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

[[image:1665301570342-765.png]]

215

216

217

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

218

219

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

220

221

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

222

223

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

246

247

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

248

249

250

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

251

252

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

253

254

255

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

256

257

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

258

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

259

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

260

261

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

262

263

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

264

265

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

266

267

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

268

269

270

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

271

272

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

273

274

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

275

276

277

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

278

279

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

280

281

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

282

283

284

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

285

286

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

287

288

|=(% style="width: 77px;" %)**Value**|(% style="width:70px" %)Reserve|(% style="width:92px" %)[[PNACKMD>>||anchor="H2.4.4A0UplinkFPORT3D42CHistoryGNSSPositioning"]]|(% style="width:48px" %)[[LON>>||anchor="H3.2.5Disable2FEnableLEDflash"]]|(% style="width:126px" %)[[Transport Mode>>||anchor="H2.9TransportMode"]]

289

290

291

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

292

293

294

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,

295

296

297

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

298

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

**Size(bytes)**

2

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

303

2

304

)))

305

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

306

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

307

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

308

309

[[image:1665301636888-168.png]]

310

311

312

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

313

314

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

315

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

316

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

317

318

319

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

320

321

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

322

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

323

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

324

325

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

326

327

328

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

329

330

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

331

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

332

333

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

334

335

1. When power is low (<2.84v), GPS won't be able to get location info and GPS feature will be disabled and the location field will be filled with 0x0FFFFFFF, 0x0FFFFFFF.

336

337

2. In this mode, the total payload will be 15 bytes, while US915/AU915 DR0 accepts only 11 bytes payload. In this case, the payload on server will be ignore and shows as below:

338

339

340

[[image:1664502116362-706.png]]

341

342

343

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

344

345

[[image:1664502166010-515.png]]

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

350

351

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

352

353

354

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

355

356

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

357

358

(((

359

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

360

)))

361

362

* > 4.0v : 80% ~~ 100%

363

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

364

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

365

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

* < 3.39v: 0~~20%

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

370

371

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

372

373

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

374

375

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

376

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

377

378

379

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

380

381

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

382

383

384

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

385

386

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

387

388

Enable/Disable LED activity for uplink

389

390

(((

391

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

)))

(((

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

)))

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

400

401

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

402

403

404

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

405

406

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

407

408

409

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

410

411

412

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)

413

414

415

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

416

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

417

**Size(bytes)**

418

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

419

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

420

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

421

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

422

423

(% class="wikigeneratedid" %)

424

[[image:1665301687277-443.png]]

425

426

427

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

428

429

430

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.

431

432

433

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

434

435

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

436

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

437

* 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

438

439

The payload is 15 bytes, as below.

440

441

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

442

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

**Size(bytes)**

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

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

448

449

450

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

451

452

453

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.

454

455

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

456

457

458

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

459

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

460

**Size(bytes)**

461

462

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

463

iBeacon MAJOR

464

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

465

iBeacon MINOR

466

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

467

iBeacon Measured Power

468

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

469

iBeacon RSSI

470

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

471

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

472

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

473

474

[[image:1664502425687-834.png]]

475

476

477

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

478

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

479

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

480

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

481

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

482

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

483

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

484

485

486

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

487

488

489

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.

490

491

492

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

493

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

494

**Size(bytes)**

495

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

496

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

497

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

498

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

499

500

(% class="wikigeneratedid" %)

501

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

502

503

504

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

505

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

506

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

507

508

509

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

510

511

512

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

513

514

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

515

516

517

[[image:1664502649601-895.png]]

Add the decoder from this link:

522

523

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

524

525

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

526

527

[[image:1664502676891-606.png]]

528

529

530

== 2.5 Integrate with Datacake ==

531

532

533

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.

534

535

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

536

537

538

[[image:1664502695771-538.png]]

539

540

541

== 2.6 Integrate with Tago ==

542

543

544

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.

545

546

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

547

548

549

[[image:1664502715371-321.png]]

550

551

552

== 2.7 Datalog Feature ==

553

554

555

total 273 entries,by default,

556

557

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

562

563

564

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

582

)))

583

584

* Server sends a downlink command to exit.

585

* User fast press the RED button 10 times.

586

587

(((

588

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

593

594

595

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.

596

597

598

== 2.10 LED Status ==

599

600

601

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

602

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

603

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

604

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

605

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

606

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

607

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

608

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

609

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

610

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

611

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

612

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

613

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

614

615

616

== 2.11 Button Function ==

617

618

619

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

620

621

[[image:1664502835802-546.png]]

622

623

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

624

625

626

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

627

628

[[image:1664502854406-763.png]]

629

630

631

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

632

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

633

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

634

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

635

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

636

637

638

== 2.12 USB Port Function ==

639

640

641

The USB interface of TrackerD has below functions:

642

643

* Power on the device

644

* Recharge the battery

645

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

646

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

647

648

649

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

650

651

652

User can configure TrackerD via AT Command or LoRaWAN Downlink.

653

654

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

655

656

657

== 3.1 Access AT Command ==

658

659

660

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.

661

662

663

[[image:1664502999401-486.png]]

664

665

666

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:

667

668

669

[[image:1664503022490-662.png]]

670

671

672

[[image:1664503035713-500.png]]

673

674

675

[[image:1664503047675-651.png]]

== 3.2 Command Set ==

680

681

=== 3.2.1 Set Transmit Interval ===

682

683

684

Set device uplink interval.

685

686

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

687

688

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

689

690

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

691

692

693

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

694

695

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

696

697

698

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

699

700

701

Set alarm packet transmit interval

702

703

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

704

705

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

706

707

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

708

709

710

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

711

712

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

713

714

715

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

716

717

718

Set Transport Mode packet transmit interval

719

720

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

721

722

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

723

724

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

725

726

727

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

728

729

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

730

731

732

=== 3.2.4 Exit Alarm ===

733

734

735

Server send downlink command to exit Alarm mode

736

737

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

738

739

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

740

741

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

742

743

744

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

745

746

747

Disable/Enable LED for position, downlink and uplink

748

749

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

750

751

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

752

753

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

754

755

756

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

757

758

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

759

760

761

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

762

763

764

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

765

766

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

767

768

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

769

770

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

771

772

773

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

774

775

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

776

777

778

=== 3.2.7 Set Positioning Mode ===

779

780

781

SMOD define how TrackerD scan and uplink data:

782

783

784

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

785

786

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

787

788

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

789

790

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

791

792

* (% style="color:red" %)**2: BLE or WiFi ONLY: **(%%)Only obtain iBeacon info via BLE and uplink or obtain WiFi ssid info via WiFi and uplink. Design for Indoor tracking.

793

794

* (% style="color:red" %)**3: GPS/BLE Hybrid: **(%%)Combination for Indoor and Outdoor tracking.Devices will try to search BLE iBeacon first. If device can't find the iBeacon, it will use GPS for positioning.

795

796

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

797

798

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

799

800

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

801

802

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

803

804

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

805

806

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

807

808

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

809

810

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

811

812

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

813

814

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

815

816

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

817

818

819

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

820

821

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

822

823

824

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

825

826

827

Set max positioning time, default is 150 seconds. TrackerD will try to get location info within this period. If fail to get position data within this time, TrackerD will use 000000 for latitude and longitude.

828

829

830

If **AT+FTIME=0**. The GPS module will be always powered and positioning. This will highly increase the power consumption (up to 50mA). When AT+FTIME=0, it will improve fix accuracy and shorten the acquire time for next uplink.

831

832

833

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

834

835

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

836

837

**Example:** AT+FTIME=150

838

839

840

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

841

842

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

843

844

845

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

846

847

848

PDOP(Position Dilution of Precision) filter, TrackerD will only accept GPS data with a lower PDOP value than pre-configure PDOP value. If device can't get a valid GPS packet within FTIME timeout, it will use the GPS data with lowest PDOP value to server.

849

850

851

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

852

853

854

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

855

856

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

857

858

859

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

860

861

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

862

863

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

864

865

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

**Disable/Enable the confirmation mode**

870

871

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

872

873

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

**~ Example:**

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

879

880

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

881

882

883

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

884

885

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

886

887

888

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

889

890

891

TrackerD will wait for ACK for each uplink, If TrackerD doesn't get ACK from the IoT server, it will consider the message doesn't arrive server and store it. TrackerD keeps sending messages in normal periodically. Once TrackerD gets ACK from a server, it will consider the network is ok and start to send the not-arrive message.

892

893

894

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

895

896

The default factory setting is 0.

897

898

899

**Command Example Function Response:**

900

901

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

902

903

904

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

905

906

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

907

908

909

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

910

911

912

BLEMASK is to filter the unwanted BLE iBeacons during scan. For example, if BLEMASK is 123456. TrackerD will only uplink UUID info which includes 123456. It will ignore all other iBeacons which doesn’t contact 123456 in the UUID.

913

914

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

915

916

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

917

918

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

919

920

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

921

922

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

923

924

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

925

926

927

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

928

929

930

WiFiMASK is to filter the unwanted WiFi SSID during scan. For example, if WiFiMASK is 123456. TrackerD will only uplink SSID info which includes 123456 as prefix. It will ignore all other WiFi which doesn’t contact 123456 in the SSID.

931

932

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

933

934

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

935

936

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

937

938

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

939

940

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

941

942

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

943

944

945

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

946

947

948

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

949

950

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

951

952

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

953

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

954

955

956

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

957

958

959

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

960

961

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

962

963

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

964

965

966

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

967

968

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

969

970

971

= 4. Setting for Different Scenarios =

= 5. Upload Firmware =

976

977

== 5.1 Firmware Change Log ==

978

979

980

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

981

982

983

== 5.2 How to upgrade firmware ==

984

985

986

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

987

988

989

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

990

991

992

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

993

994

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

995

996

997

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

998

999

1000

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

1001

1002

1003

[[image:1664503563660-578.png]]

1004

1005

1006

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

1011

1012

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

1013

1014

1015

**Users need to use below files:**

boot_app0.bin @0e000

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

1020

1021

1022

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

After upgrade finish, it will show finish as below:

1027

1028

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

= 6. Developer Guide =

1033

1034

== 6.1 Compile Source Code ==

1035

1036

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

1037

1038

1039

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

1040

1041

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

1042

1043

1044

[[image:1664503635019-941.png]]

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

1049

1050

[[image:1664503715811-892.png]]

1051

1052

1053

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

1054

1055

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

1066

1067

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

1068

1069

1070

[[image:1664503752288-974.png]]

1071

1072

1073

== 6.2 Source Code ==

1074

1075

1076

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

1077

1078

[[image:1664503794261-827.png]]

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

1083

1084

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

1089

1090

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

= 7. FAQ =

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

1096

1097

1098

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

1099

1100

1101

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

1102

1103

1104

[[image:1664499635206-262.png]]

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

1109

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

1110

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

1111

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

1112

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

1113

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

1114

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

1115

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

1116

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

1117

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

1118

1119

1120

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

1121

1122

=== 7.3.1 Serial port utility ===

1123

1124

1125

Serial port utility requires you to automatically add data streams.

1126

1127

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

1128

1129

(% class="wikigeneratedid" %)

1130

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

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

1135

1136

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

1137

1138

1139

=== 7.3.2 SecureCRT ===

1140

1141

1142

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.

1143

1144

1145

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

1146

1147

1148

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

=== 7.3.3 PUTTY ===

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

1155

1156

1157

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.

1158

1159

1160

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

1161

1162

1163

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

1164

1165

1166

(% class="box infomessage" %)

1167

(((

1168

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

1169

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

1170

)))

1171

1172

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

1173

1174

1175

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

1180

1181

1182

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

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

1187

1188

1189

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

1194

1195

1196

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

1197

1198

1199

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

1200

1201

1202

= 8 Trouble Shooting =

1203

1204

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

1221

1222

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

1231

1232

1233

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

1234

1235

1236

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

1237

1238

1239

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

1240

1241

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

1242

1243

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

1244

1245

1246

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

1247

1248

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

1254

1255

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

1256

1257

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

1258

1259

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

1260

1261

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

1267

1268

AT+APPEUI=D23345667BCBCCAF

1269

1270

AT+APPKEY=F402A1A7A350445A7CD2DEA95511BFA1

1271

1272

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

1273

1274

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

1275

1276

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

1281

1282

1283

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

1284

1285

1286

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

1287

1288

1289

Please download version 1.4.2 again

1290

1291

1292

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

1293

1294

1295

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

1296

1297

2) Set PDOP to a higher value.

1298

1299

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

1300

1301

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

1302

1303

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

1304

1305

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

1312

1313

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

1314

1315

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

1316

1317

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

1318

1319

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

1320

1321

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

1322

1323

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

1324

1325

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

1326

1327

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

= 10. Packing Info =

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

1334

1335

* TrackerD LoRaWAN GPS/BLE Tracker x 1

1336

1337

* USB recharge & program cable x 1

1338

1339

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

1340

1341

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

1350

1351

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

1358

1359

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

1360

1361

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

Wiki source code of TrackerD -LoRaWAN Tracker User Manual