TrackerD -LoRaWAN Tracker User Manual

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

23

)))

24

25

(((

26

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

27

28

(((

29

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

)))

(((

The LoRa wireless technology used in TrackerD allows the user to send data and reach extremely long ranges at low data-rates. It provides ultra-long range spread spectrum communication and high interference immunity whilst minimizing current consumption. It targets professional tracking services.

)))

)))

(((

TrackerD is equipped with a (% style="color:blue" %)**1000mAh Li-on rechargeable battery**(%%). Each TrackerD has a worldwide unique OTAA keys to join the LoRaWAN network.

)))

[[image:1664499921684-770.png]]

44

45

46

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

== 1.2 Specifications ==

51

52

53

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

54

55

* Espressif ESP32 PICO D4

56

* MCU: ESP32 PICO D4

57

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

58

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

59

* Integrated SPI flash : 4 MB

* RAM: 448 KB

* EEPROM: 520 KB

* Clock Speed: 32Mhz

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

65

66

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

67

* Operating Temperature: -40 ~~ 60°C

68

69

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

70

71

* Frequency Range,

72

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

73

* 168 dB maximum link budget.

74

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

75

* +14 dBm high efficiency PA.

76

* Programmable bit rate up to 300 kbps.

77

* High sensitivity: down to -148 dBm.

78

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

79

* Excellent blocking immunity.

80

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

81

* Fully integrated synthesizer with a resolution of 61 Hz.

82

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

83

* Built-in bit synchronizer for clock recovery.

84

* Preamble detection.

85

* 127 dB Dynamic Range RSSI.

86

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

87

* Packet engine up to 256 bytes with CRC.

88

* LoRaWAN 1.0.3 Specification

89

90

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

91

92

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

93

94

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

95

96

* Sleeping Mode: 200uA

97

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

98

* Tracking: max: 38mA

== 1.3 Features ==

* LoRaWAN 1.0.3 Class A

106

* ESP32 PICO D4

107

* SX1276/78 Wireless Chip

108

* Arduino IDE Compatible

109

* Open source hardware / software

110

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

111

* Built-in3 axis accelerometer (LIS3DH)

112

* Humidity / temperature sensor : GXCAS Technology GXHT3X

113

* Motion sensing capability

114

* Power Monitoring

115

* Charging circuit via USB port

116

* 1000mA Li-on Battery power

117

* Tri-color LED, Alarm button

* Datalog

== 1.4 Applications ==

123

124

125

* Logistics and Supply Chain Management

* Human tracking

= 2. Use TrackerD =

== 2.1 How it works? ==

134

135

136

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.

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

141

142

143

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.

144

145

146

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

151

152

153

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

154

155

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

156

157

158

[[image:1664501677253-891.png]]

159

160

161

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

162

163

164

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

165

166

167

[[image:1664501711466-918.png]]

[[image:1664501721248-725.png]]

172

173

174

[[image:1664501734705-405.png]]

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

179

180

181

[[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**:(%%) Power on TrackerD by using the on board switch.

186

187

188

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

== 2.3 Positioning Mode(SMOD) ==

193

194

195

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

196

197

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

198

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

199

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

200

201

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

== 2.4 Uplink Payload ==

206

207

208

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

209

210

211

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.

212

213

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

214

215

216

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

[[image:1665301570342-765.png]]

221

222

223

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

224

225

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

226

227

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

228

229

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

252

253

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

254

255

256

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

257

258

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

259

260

261

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

262

263

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

264

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

265

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

266

267

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

268

269

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

270

271

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

272

273

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

274

275

276

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

277

278

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

279

280

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

281

282

283

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

284

285

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

286

287

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

288

289

290

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

291

292

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

293

294

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

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

299

300

301

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,

302

303

304

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

305

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

**Size(bytes)**

2

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

310

2

311

)))

312

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

313

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

314

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

315

316

[[image:1665301636888-168.png]]

317

318

319

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

320

321

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

322

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

323

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

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

328

329

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

330

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

331

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

332

333

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

334

335

336

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

337

338

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

339

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

340

341

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

342

343

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.

344

345

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:

346

347

348

[[image:1664502116362-706.png]]

349

350

351

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

352

353

[[image:1664502166010-515.png]]

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

358

359

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

360

361

362

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

363

364

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

365

366

(((

367

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

368

)))

369

370

* > 4.0v : 80% ~~ 100%

371

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

372

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

373

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

* < 3.39v: 0~~20%

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

379

380

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

381

382

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

383

384

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

385

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

386

387

388

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

389

390

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

391

392

393

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

394

395

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

396

397

Enable/Disable LED activity for uplink

398

399

(((

400

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

)))

(((

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

)))

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

409

410

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

411

412

413

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

414

415

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

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

420

421

422

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)

423

424

425

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

426

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

427

**Size(bytes)**

428

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

429

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

430

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

431

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

432

433

(% class="wikigeneratedid" %)

434

[[image:1665301687277-443.png]]

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

439

440

441

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.

442

443

444

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

445

446

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

447

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

448

* 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

449

450

The payload is 15 bytes, as below.

451

452

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

453

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

**Size(bytes)**

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

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

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

463

464

465

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.

466

467

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

468

469

470

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

471

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

472

**Size(bytes)**

473

474

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

475

iBeacon MAJOR

476

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

477

iBeacon MINOR

478

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

479

iBeacon Measured Power

480

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

481

iBeacon RSSI

482

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

483

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

484

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

485

486

[[image:1664502425687-834.png]]

487

488

489

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

490

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

491

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

492

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

493

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

494

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

495

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

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

500

501

502

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.

503

504

505

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

506

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

507

**Size(bytes)**

508

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

509

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

510

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

511

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

512

513

(% class="wikigeneratedid" %)

514

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

515

516

517

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

518

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

519

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

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

524

525

526

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

527

528

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

529

530

531

[[image:1664502649601-895.png]]

532

533

534

Add the decoder from this link:

535

536

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

537

538

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

539

540

[[image:1664502676891-606.png]]

== 2.5 Integrate with Datacake ==

545

546

547

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.

548

549

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

550

551

552

[[image:1664502695771-538.png]]

== 2.6 Integrate with Tago ==

557

558

559

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.

560

561

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

562

563

564

[[image:1664502715371-321.png]]

== 2.7 Datalog Feature ==

569

570

571

total 273 entries,by default,

572

573

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

578

579

580

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

599

)))

600

601

* Server sends a downlink command to exit.

602

* User fast press the RED button 10 times.

603

604

(((

605

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

611

612

613

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.

== 2.10 LED Status ==

618

619

620

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

621

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

622

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

623

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

624

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

625

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

626

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

627

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

628

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

629

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

630

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

631

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

632

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

== 2.11 Button Function ==

637

638

639

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

640

641

[[image:1664502835802-546.png]]

642

643

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

644

645

646

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

647

648

[[image:1664502854406-763.png]]

649

650

651

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

652

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

653

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

654

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

655

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

== 2.12 USB Port Function ==

660

661

662

The USB interface of TrackerD has below functions:

663

664

* Power on the device

665

* Recharge the battery

666

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

667

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

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

672

673

674

User can configure TrackerD via AT Command or LoRaWAN Downlink.

675

676

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

== 3.1 Access AT Command ==

681

682

683

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.

684

685

686

[[image:1664502999401-486.png]]

687

688

689

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:

690

691

692

[[image:1664503022490-662.png]]

693

694

695

[[image:1664503035713-500.png]]

696

697

698

[[image:1664503047675-651.png]]

== 3.2 Command Set ==

703

704

705

=== 3.2.1 Set Transmit Interval ===

706

707

708

Set device uplink interval.

709

710

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

711

712

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

713

714

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

715

716

717

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

718

719

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

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

724

725

726

Set alarm packet transmit interval

727

728

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

729

730

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

731

732

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

733

734

735

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

736

737

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

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

742

743

744

Set Transport Mode packet transmit interval

745

746

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

747

748

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

749

750

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

751

752

753

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

754

755

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

=== 3.2.4 Exit Alarm ===

760

761

762

Server send downlink command to exit Alarm mode

763

764

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

765

766

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

767

768

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

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

773

774

775

Disable/Enable LED for position, downlink and uplink

776

777

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

778

779

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

780

781

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

782

783

784

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

785

786

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

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

791

792

793

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

794

795

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

796

797

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

798

799

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

800

801

802

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

803

804

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

=== 3.2.7 Set Positioning Mode ===

809

810

811

SMOD define how TrackerD scan and uplink data:

812

813

814

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

815

816

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

817

818

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

819

820

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

821

822

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

823

824

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

825

826

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

827

828

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

829

830

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

831

832

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

833

834

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

835

836

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

837

838

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

839

840

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

841

842

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

843

844

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

845

846

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

847

848

849

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

850

851

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

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

856

857

858

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.

859

860

861

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.

862

863

864

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

865

866

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

867

868

**Example:** AT+FTIME=150

869

870

871

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

872

873

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

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

878

879

880

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.

881

882

883

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

884

885

886

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

887

888

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

889

890

891

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

892

893

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

894

895

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

896

897

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

Disable/Enable the confirmation mode

902

903

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

904

905

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

**~ Example:**

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

911

912

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

913

914

915

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

916

917

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

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

922

923

924

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.

925

926

927

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

928

929

The default factory setting is 0.

930

931

932

**Command Example Function Response:**

933

934

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

935

936

937

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

938

939

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

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

944

945

946

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.

947

948

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

949

950

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

951

952

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

953

954

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

955

956

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

957

958

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

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

963

964

965

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.

966

967

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

968

969

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

970

971

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

972

973

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

974

975

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

976

977

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

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

982

983

984

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

985

986

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

987

988

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

989

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

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

994

995

996

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

997

998

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

999

1000

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

1001

1002

1003

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

1004

1005

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

= 4. Setting for Different Scenarios =

= 5. Upload Firmware =

1014

1015

1016

== 5.1 Firmware Change Log ==

1017

1018

1019

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

== 5.2 How to upgrade firmware ==

1024

1025

1026

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

1027

1028

1029

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

1030

1031

1032

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

1033

1034

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

1035

1036

1037

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

1038

1039

1040

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

1041

1042

1043

[[image:1664503563660-578.png]]

1044

1045

1046

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

1051

1052

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

1053

1054

1055

Users need to use below files:

boot_app0.bin @0e000

ESP_LORA-eeprom-class.bin @ 0x10000

1060

1061

1062

[[image:1664503593459-435.png]]

After upgrade finish, it will show finish as below:

1067

1068

[[image:1664503611848-385.png]]

= 6. Developer Guide =

1073

1074

1075

== 6.1 Compile Source Code ==

1076

1077

1078

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

1079

1080

1081

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

1082

1083

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

1084

1085

1086

[[image:1664503635019-941.png]]

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

1091

1092

[[image:1664503715811-892.png]]

1093

1094

1095

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

1096

1097

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

1108

1109

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

1110

1111

1112

[[image:1664503752288-974.png]]

== 6.2 Source Code ==

1117

1118

1119

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

1120

1121

[[image:1664503794261-827.png]]

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

1126

1127

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

1132

1133

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

= 7. FAQ =

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

1141

1142

1143

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

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

1148

1149

1150

[[image:1664499635206-262.png]]

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

1155

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

1156

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

1157

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

1158

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

1159

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

1160

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

1161

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

1162

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

1163

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

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

1168

1169

1170

=== 7.3.1 Serial port utility ===

1171

1172

1173

Serial port utility requires you to automatically add data streams.

1174

1175

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

1176

1177

1178

(% class="wikigeneratedid" %)

1179

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

1180

1181

1182

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

1183

1184

1185

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

=== 7.3.2 SecureCRT ===

1190

1191

1192

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.

1193

1194

1195

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

1196

1197

1198

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

=== 7.3.3 PUTTY ===

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

1206

1207

1208

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.

1209

1210

1211

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

= 8 Trouble Shooting =

1216

1217

1218

== 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 The reason why it has been restarted after upgrading（V.1.4.1） ==

(((

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-20221107145243-1.png||height="695" width="443"]]

= 9. Order Info =

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

1252

1253

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

1254

1255

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

1256

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

1257

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

1258

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

1259

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

1260

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

1261

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

= 10. Packing Info =

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

1269

1270

* TrackerD LoRaWAN GPS/BLE Tracker x 1

1271

* USB recharge & program cable x 1

1272

1273

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

1274

1275

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

1284

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

1292

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

1293