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.

37

)))

38

39

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

40

41

42

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

43

44

45

== 1.2 Specifications ==

46

47

48

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

49

50

* Espressif ESP32 PICO D4

51

* MCU: ESP32 PICO D4

52

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

53

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

54

* Integrated SPI flash : 4 MB

* RAM: 448 KB

* EEPROM: 520 KB

* Clock Speed: 32Mhz

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

60

61

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

62

* Operating Temperature: -40 ~~ 60°C

63

64

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

65

66

* Frequency Range,

67

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

68

* 168 dB maximum link budget.

69

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

70

* +14 dBm high efficiency PA.

71

* Programmable bit rate up to 300 kbps.

72

* High sensitivity: down to -148 dBm.

73

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

74

* Excellent blocking immunity.

75

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

76

* Fully integrated synthesizer with a resolution of 61 Hz.

77

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

78

* Built-in bit synchronizer for clock recovery.

79

* Preamble detection.

80

* 127 dB Dynamic Range RSSI.

81

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

82

* Packet engine up to 256 bytes with CRC.

83

* LoRaWAN 1.0.3 Specification

84

85

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

86

87

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

88

89

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

90

91

* Sleeping Mode: 200uA

92

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

93

* Tracking: max: 38mA

== 1.3 Features ==

* LoRaWAN 1.0.3 Class A

100

* ESP32 PICO D4

101

* SX1276/78 Wireless Chip

102

* Arduino IDE Compatible

103

* Open source hardware / software

104

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

105

* Built-in3 axis accelerometer (LIS3DH)

106

* Humidity / temperature sensor : GXCAS Technology GXHT3X

107

* Motion sensing capability

108

* Power Monitoring

109

* Charging circuit via USB port

110

* 1000mA Li-on Battery power

111

* Tri-color LED, Alarm button

* Datalog

== 1.4 Applications ==

116

117

118

* 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||_mstalt="293306"]]

The LPS8N is already set to connect to [[TTN V3 network >>url:https://eu1.cloud.thethings.network/]]. What the rest need to is register this device in TTN V3:

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||_mstalt="296569"]]

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||_mstalt="295828"]]

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

162

163

164

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

**__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||_mstalt="298233" 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||_mstalt="295061"]]

178

179

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

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||_mstalt="294580"]]

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

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

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||_mstalt="298012"]]

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||_mstalt="293306"]]

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||_mstalt="291395"]]

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

* < 3.39v: 0~~20%

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

365

366

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

367

368

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

369

370

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

371

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

372

373

374

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

375

376

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

377

378

379

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

380

381

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

382

383

Enable/Disable LED activity for uplink

384

385

(((

386

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

)))

(((

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

)))

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

395

396

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

397

398

399

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

400

401

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

402

403

404

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

405

406

407

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)

408

409

410

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

411

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

412

**Size(bytes)**

413

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

414

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

415

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

416

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

417

418

(% class="wikigeneratedid" %)

419

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

420

421

422

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

423

424

425

Set [[PNACKMD=1>>||anchor="H3.2.11A0AutoSendNone-ACKmessages"]], and TrackerD will wait for ACK for every uplink, when there is no LoRaWAN network, TrackerD will mark these records with non-ack messages and store the sensor data, and it will send all messages (10s interval) after the network recovery.

426

427

428

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

429

430

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

431

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

432

* 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

433

434

The payload is 15 bytes, as below.

435

436

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

437

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

**Size(bytes)**

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

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

443

444

445

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

446

447

448

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.

449

450

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

451

452

453

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

454

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

455

**Size(bytes)**

456

457

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

458

iBeacon MAJOR

459

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

460

iBeacon MINOR

461

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

462

iBeacon Measured Power

463

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

464

iBeacon RSSI

465

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

466

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

467

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

468

469

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

470

471

472

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

473

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

474

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

475

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

476

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

477

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

478

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

479

480

481

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

482

483

484

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.

485

486

487

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

488

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

489

**Size(bytes)**

490

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

491

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

492

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

493

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

494

495

(% class="wikigeneratedid" %)

496

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

497

498

499

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

500

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

501

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

502

503

504

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

505

506

507

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

508

509

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

510

511

512

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

Add the decoder from this link:

517

518

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

519

520

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

521

522

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

523

524

525

== 2.5 Integrate with Datacake ==

526

527

528

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.

529

530

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

531

532

533

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

534

535

536

== 2.6 Integrate with Tago ==

537

538

539

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.

540

541

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

542

543

544

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

545

546

547

== 2.7 Datalog Feature ==

548

549

550

total 273 entries,by default,

551

552

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

Example use case.

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

557

558

559

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

== 2.8 Alarm Mode ==

(((

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

)))

(((

Once enter Alarm mode, the (% style="color:green" %)**GREEN LED**(%%) will flash 3 times, the buzzer will alarm for 5 seconds, then TrackerD will immediately send a packet without location info and then send a data packet with GPS positioning information. After that, the device will send 60 packets at 1-minute intervals. The Alarm flag in the payload will be set for the next 60 packets unless exits alert mode.

)))

(((

**Two ways to exit alarm mode:**

577

)))

578

579

* Server sends a downlink command to exit.

580

* User fast press the RED button 10 times.

581

582

(((

583

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

588

589

590

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.

591

592

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

593

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

594

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

595

596

597

== 2.10 LED Status ==

598

599

600

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

601

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

602

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

603

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

604

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

605

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

606

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

607

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

608

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

609

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

610

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

611

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

612

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

613

614

615

== 2.11 Button Function ==

616

617

618

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

619

620

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

621

622

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

623

624

625

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

626

627

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

628

629

630

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

631

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

632

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

633

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

634

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

635

636

637

== 2.12 USB Port Function ==

638

639

640

The USB interface of TrackerD has below functions:

641

642

* Power on the device

643

* Recharge the battery

644

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

645

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

646

647

648

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

649

650

651

User can configure TrackerD via AT Command or LoRaWAN Downlink.

652

653

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

654

655

656

== 3.1 Access AT Command ==

657

658

659

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.

660

661

662

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

663

664

665

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:

666

667

668

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

669

670

671

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

672

673

674

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

675

676

677

== 3.2 Command Set ==

678

679

=== 3.2.1 Set Transmit Interval ===

680

681

682

Set device uplink interval.

683

684

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

685

686

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

687

688

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

689

690

691

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

692

693

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

694

695

696

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

697

698

699

Set alarm packet transmit interval

700

701

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

702

703

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

704

705

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

706

707

708

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

709

710

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

711

712

713

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

714

715

716

Set Transport Mode packet transmit interval

717

718

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

719

720

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

721

722

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

723

724

725

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

726

727

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

728

729

730

=== 3.2.4 Exit Alarm ===

731

732

733

Server send downlink command to exit Alarm mode

734

735

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

736

737

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

738

739

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

740

741

742

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

743

744

745

Disable/Enable LED for position, downlink and uplink

746

747

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

748

749

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

750

751

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

752

753

754

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

755

756

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

757

758

759

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

760

761

762

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

763

764

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

765

766

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

767

768

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

769

770

771

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

772

773

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

774

775

776

=== 3.2.7 Set Positioning Mode ===

777

778

779

SMOD define how TrackerD scan and uplink data:

780

781

782

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

783

784

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

785

786

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

787

788

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

789

790

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

791

792

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

793

794

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

795

796

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

797

798

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

799

800

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

801

802

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

803

804

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

805

806

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

807

808

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

809

810

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

811

812

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

813

814

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

815

816

817

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

818

819

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

820

821

822

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

823

824

825

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.

826

827

828

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.

829

830

831

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

832

833

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

834

835

**Example:** AT+FTIME=150

836

837

838

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

839

840

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

841

842

843

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

844

845

846

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.

847

848

849

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

850

851

852

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

853

854

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

855

856

857

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

858

859

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

860

861

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

862

863

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

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

868

869

870

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

871

872

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

**~ Example:**

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

878

879

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

880

881

882

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

883

884

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

885

886

887

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

888

889

890

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.

891

892

893

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

894

895

The default factory setting is 0.

896

897

898

**Command Example Function Response:**

899

900

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

901

902

903

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

904

905

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

906

907

908

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

909

910

911

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.

912

913

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

914

915

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

916

917

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

918

919

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

920

921

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

922

923

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

924

925

926

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

927

928

929

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.

930

931

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

932

933

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

934

935

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

936

937

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

938

939

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

940

941

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

942

943

944

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

945

946

947

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

948

949

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

950

951

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

952

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

953

954

955

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

956

957

958

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

959

960

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

961

962

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

963

964

965

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

966

967

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

968

969

970

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

971

972

973

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

974

975

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

976

977

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

Example:

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

982

983

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

984

985

986

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

987

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

988

989

990

= 4. Setting for Different Scenarios =

= 5. Upload Firmware =

995

996

== 5.1 Firmware Change Log ==

997

998

999

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

1000

1001

1002

== 5.2 How to upgrade firmware ==

1003

1004

1005

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

1006

1007

1008

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

1009

1010

1011

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

1012

1013

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

1014

1015

1016

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

1017

1018

1019

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

1020

1021

1022

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

1023

1024

1025

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

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

1030

1031

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

1032

1033

1034

**Users need to use below files:**

boot_app0.bin @0e000

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

1039

1040

1041

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

After upgrade finish, it will show finish as below:

1046

1047

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

= 6. Developer Guide =

1052

1053

== 6.1 Compile Source Code ==

1054

1055

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

1056

1057

1058

* **Download the latest Arduino software (IDE) from the Arduino official website: [[https:~~/~~/www.arduino.cc/en/Main/Software>>url:https://www.arduino.cc/en/Main/Software]]**

1059

1060

Install IDE on PC, open and click (% style="color:#037691" %)**File ~-~-> Preference**,(%%) add the following URL: [[https:~~/~~/dl.espressif.com/dl/package_esp32_index.json>>url:https://links.jianshu.com/go?to=https%3A%2F%2Fdl.espressif.com%2Fdl%2Fpackage_esp32_index.json]]

1061

1062

1063

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

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

1068

1069

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

1070

1071

1072

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

1073

1074

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

**~ Figure1**

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

**Figure2**

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

1085

1086

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

1087

1088

1089

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

1090

1091

1092

== 6.2 Source Code ==

1093

1094

1095

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

1096

1097

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

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

1102

1103

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

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

1108

1109

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

= 7. FAQ =

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

1115

1116

1117

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

1118

1119

1120

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

1121

1122

1123

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

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

1128

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

1129

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

1130

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

1131

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

1132

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

1133

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

1134

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

1135

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

1136

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

1137

1138

1139

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

1140

1141

=== 7.3.1 Serial port utility ===

1142

1143

1144

Serial port utility requires you to automatically add data streams.

1145

1146

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

1147

1148

(% class="wikigeneratedid" %)

1149

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

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

1154

1155

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

1156

1157

1158

=== 7.3.2 SecureCRT ===

1159

1160

1161

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.

1162

1163

1164

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

1165

1166

1167

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

=== 7.3.3 PUTTY ===

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

1174

1175

1176

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.

1177

1178

1179

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

1180

1181

1182

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

1183

1184

1185

(% class="box infomessage" %)

1186

(((

1187

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

1188

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

1189

)))

1190

1191

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

1192

1193

1194

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

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

1199

1200

1201

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

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

1206

1207

1208

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

**4. In other frequency bands in AS923, you need to find Lorabase_as923.H, path arduino-lmic \ src \ lmic, as shown in the figure below.**

1213

1214

1215

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

1216

1217

1218

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

1219

1220

1221

= 8 Trouble Shooting =

1222

1223

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

(((

Before firmware v1.4.0: When the Transport Mode is enabled ((% style="color:blue" %)**AT+INTWK=1**(%%)), the **TDC** needs to be greater than **MTDC**, otherwise, TDC setting will because 4294947296 after wakre up from motion. This bug is fixed in firmware v1.4.1

)))

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

(((

ESP32 is not able to accept the Interrupt from UART after wake up from deep sleep mode. User need to press the button (one click) and trackerD will be able to accept UART command, it there is no action in UART for 15 seconds. it will go to deep sleep mode.

)))

== 8.3 Problem after Upgrading Firmware ==

1240

1241

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

**Error Output**

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

(((

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

1252

1253

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

)))

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

1258

1259

1260

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

1261

1262

1263

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

1264

1265

1266

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

1267

1268

1269

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

1270

1271

1272

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

1273

1274

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

**Figure 2**

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

1280

1281

1282

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

1283

1284

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

1285

1286

1287

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

1288

1289

1290

Please (% style="color:blue" %)**AT+FDR**(%%) which will reset all settings to factory settings. , and then input the following keys by the information on the label.

1291

1292

After AT+FDR. please set

1293

1294

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

1295

1296

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

**Example:**

AT+PDOP=7.00

AT+FTIME=180

AT+DEUI=70B3D57ED0053981

1305

1306

AT+APPEUI=D23345667BCBCCAF

1307

1308

AT+APPKEY=F402A1A7A350445A7CD2DEA95511BFA1

1309

1310

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

1311

1312

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

1313

1314

AT+APPSKEY=dacce2299ecd97a73ee3f80b5a46a559 ( no need for OTAA)

1315

1316

1317

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

1318

1319

1320

Please download version 1.4.2 again

1321

1322

1323

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

1324

1325

1326

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

1327

1328

2) Set PDOP to a higher value.

1329

1330

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

1331

1332

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

1333

1334

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

1335

1336

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

1337

1338

1339

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

1340

1341

1342

When upgrading, use the erase button to upgrade

1343

1344

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

1345

1346

1347

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

1348

1349

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

1350

1351

1352

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

1353

1354

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

1355

1356

1357

Reboot information after upgrade

1358

1359

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

1360

1361

1362

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

1363

1364

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

1365

1366

1367

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

1368

1369

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

1370

1371

1372

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

1373

1374

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

= 9. Order Info =

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

1381

1382

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

1383

1384

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

1385

1386

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

1387

1388

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

1389

1390

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

1391

1392

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

1393

1394

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

1395

1396

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

= 10. Packing Info =

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

1403

1404

* TrackerD LoRaWAN GPS/BLE Tracker x 1

1405

1406

* USB recharge & program cable x 1

1407

1408

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

1409

1410

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

1419

1420

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

1427

1428

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

1429