TrackerD -LoRaWAN Tracker User Manual

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

23

)))

24

25

(((

26

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

27

28

(((

29

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

)))

(((

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

)))

(((

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

38

)))

39

40

[[image:image-20230213110119-1.png||height="382" width="834"]]

41

42

43

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

44

45

46

== 1.2 Specifications ==

47

48

49

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

50

51

* Espressif ESP32 PICO D4

52

* MCU: ESP32 PICO D4

53

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

54

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

55

* Integrated SPI flash : 4 MB

* RAM: 448 KB

* EEPROM: 520 KB

* Clock Speed: 32Mhz

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

61

62

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

63

* Operating Temperature: -40 ~~ 60°C

64

65

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

66

67

* Frequency Range,

68

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

69

* 168 dB maximum link budget.

70

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

71

* +14 dBm high efficiency PA.

72

* Programmable bit rate up to 300 kbps.

73

* High sensitivity: down to -148 dBm.

74

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

75

* Excellent blocking immunity.

76

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

77

* Fully integrated synthesizer with a resolution of 61 Hz.

78

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

79

* Built-in bit synchronizer for clock recovery.

80

* Preamble detection.

81

* 127 dB Dynamic Range RSSI.

82

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

83

* Packet engine up to 256 bytes with CRC.

84

* LoRaWAN 1.0.3 Specification

85

86

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

87

88

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

89

90

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

91

92

* Sleeping Mode: 200uA

93

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

94

* Tracking: max: 38mA

95

96

(% style="display:none" %)

== 1.3 Features ==

* LoRaWAN 1.0.3 Class A

103

* ESP32 PICO D4

104

* SX1276/78 Wireless Chip

105

* Arduino IDE Compatible

106

* Open source hardware / software

107

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

108

* Built-in3 axis accelerometer (LIS3DH)

109

* Humidity / temperature sensor : GXCAS Technology GXHT3X

110

* Motion sensing capability

111

* Power Monitoring

112

* Charging circuit via USB port

113

* 1000mA Li-on Battery power

114

* Tri-color LED, Alarm button

115

* Datalog

116

117

(% style="display:none" %)

118

119

120

== 1.4 Applications ==

121

122

123

* Logistics and Supply Chain Management

124

* Human tracking

125

126

(% style="display:none" %)

= 2. Use TrackerD =

== 2.1 How it works? ==

132

133

134

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.

135

136

137

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

138

139

140

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.

141

142

143

[[image:image-20230213110214-2.png||height="388" width="847"]]

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

148

149

150

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

151

152

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

153

154

155

[[image:image-20230426085815-1.png||height="259" width="558"]]

156

157

158

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

159

160

161

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

162

163

164

[[image:1664501711466-918.png||_mstalt="295828"]]

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

169

170

171

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

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

176

177

178

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

183

184

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

185

186

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

187

188

189

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

190

191

192

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

202

203

204

== 2.4 Uplink Payload ==

205

206

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

207

208

209

Uplink the device configures with (% style="color:blue" %)**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.

210

211

Use can also get the Device Status uplink through the downlink command: (% style="color:#037691" %)**Downlink: 0x2301**

212

213

214

(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:440px" %)

215

|(% style="background-color:#d9e2f3; color:#0070c0; width:60px" %)**Size(bytes)**|=(% style="width: 70px;background-color:#D9E2F3;color:#0070C0" %)1|=(% style="width: 70px;background-color:#D9E2F3;color:#0070C0" %)**2**|=(% style="width: 70px;background-color:#D9E2F3;color:#0070C0" %)**1**|=(% style="width: 50px;background-color:#D9E2F3;color:#0070C0" %)**1**|=(% style="width: 30px;background-color:#D9E2F3;color:#0070C0" %)2|=(% style="width: 40px;background-color:#D9E2F3;color:#0070C0" %)1|=(% style="width: 40px;background-color:#D9E2F3;color:#0070C0" %)1

216

217

218

[[image:1665301570342-765.png||_mstalt="294580"]]

219

220

221

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

222

223

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

224

225

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

226

227

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

250

251

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

252

253

254

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

255

256

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

257

258

259

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

260

261

(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:270px" %)

262

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

263

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

264

265

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

266

267

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

268

269

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

270

271

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

272

273

274

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

275

276

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

277

278

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

279

280

281

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

282

283

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

284

285

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

286

287

288

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

289

290

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

291

292

|(% style="width:75px" %)**Value**|(% style="width:68px" %)Reserve|(% style="width:87px" %)[[PNACKMD>>||anchor="H2.4.4A0UplinkFPORT3D42CHistoryGNSSPositioning"]]|(% style="width:49px" %)[[LON>>||anchor="H3.2.5Disable2FEnableLEDflash"]]|(% style="width:126px" %)[[Transport Mode>>||anchor="H2.9TransportMode"]]

293

294

(% style="display:none" %)

295

296

297

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

298

299

300

Users can use (% style="color:blue" %)**AT+SMOD=1,0,0**(%%) to enable uploading on-board Temperature and humidity values, and the total payload will be 15 bytes,

301

302

303

(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:320px" %)

304

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

**Size(bytes)**

2

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

309

2

310

)))

311

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

312

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

313

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

314

315

[[image:1665301636888-168.png||_mstalt="298012"]]

316

317

318

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

319

320

(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:321px" %)

321

|(% style="width:60px" %)**Size(bit)**|(% style="width:60px" %)1 bit|(% style="width:134px" %)1 bit|(% style="width:67px" %)14 bits

322

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

323

324

(% style="display:none" %)

325

326

327

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

328

329

(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:184px" %)

330

|(% style="width:68px" %)**Size(bit)**|(% style="width:61px" %)2 bits|(% style="width:55px" %)1 bit

331

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

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

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

374

* < 3.39v: 0~~20%

375

376

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

377

378

379

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

380

381

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

382

383

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

384

385

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

386

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

387

388

389

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

390

391

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

392

393

394

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

395

396

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

397

398

Enable/Disable LED activity for uplink

399

400

(((

401

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

)))

(((

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

)))

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

410

411

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

412

413

414

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

415

416

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

417

418

419

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

420

421

422

The default uplink payload includes total 11 bytes ((% style="color:blue" %)**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" cellspacing="5" style="background-color:#f2f2f2; width:300px" %)

426

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

427

**Size(bytes)**

428

)))|(% style="width:60px" %)4|(% style="width:60px" %)4|(% style="width:70px" %)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||_mstalt="296140"]]

435

436

437

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

438

439

440

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.

441

442

443

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

444

445

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

446

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

447

* 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

448

449

The payload is 15 bytes, as below.

450

451

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

|(((

**Size(bytes)**

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

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

458

459

460

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

461

462

463

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.

464

465

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

466

467

468

(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:450px" %)

469

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

470

**Size(bytes)**

471

472

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

473

iBeacon MAJOR

474

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

475

iBeacon MINOR

476

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

477

iBeacon Measured Power

478

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

479

iBeacon RSSI

480

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

481

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

482

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

483

484

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

485

486

487

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

488

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

489

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

490

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

491

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

492

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

493

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

494

495

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

496

497

498

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

499

500

501

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

502

503

(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:284.818px" %)

504

|(% style="width:97px" %)**Size(bytes)**|(% style="width:103px" %)2|(% style="width:81px" %)1

505

|(% style="width:97px" %)**Value**|(% style="width:103px" %)[[Alarm & BAT>>path:#HAlarm26BAT:]]|(% style="width:81px" %)Mod+lon

506

507

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

508

509

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

510

511

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

512

513

**mod** = bytes[2] & 0xC0;

514

515

**Lon**=(bytes[2] & 0x20)

516

517

518

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

519

520

521

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.

522

523

524

(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:348px" %)

525

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

526

**Size(bytes)**

527

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

528

|(% style="width:69px" %)**Value**|(% style="width:48px" %)SSID|(% style="width:48px" %)RSSI|(% style="width:103px" %)(((

529

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

530

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

531

532

(% class="wikigeneratedid" %)

533

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

534

535

536

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

537

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

538

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

539

540

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

541

542

543

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

544

545

546

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

547

548

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

549

550

551

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

Add the decoder from this link: [[https:~~/~~/github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD>>https://github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD]]

556

557

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

558

559

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

560

561

562

== 2.5 Integrate with Datacake ==

563

564

565

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.

566

567

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

568

569

570

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

571

572

573

== 2.6 Integrate with Tago ==

574

575

576

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.

577

578

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

579

580

581

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

582

583

584

== 2.7 Integrate with Node-red ==

585

586

587

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

588

589

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

590

591

592

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

593

594

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

595

596

597

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

598

599

(% style="color:red" %)**Note: If you are using NODE-RED for the first time, please search and install the two plug-ins in the figure below in node-red to fully use the flow template.**

600

601

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

602

603

604

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

3. Display the map

Enter the link to the map:

609

610

Change its suffix to ditu：http:~/~/119.91.62.30:1880/**ditu/**

611

612

**~ **[[image:image-20230308115430-1.png||height="548" width="1041"]]

613

614

615

Hit all input in input stream

616

617

[[image:image-20230308115616-2.png||height="563" width="1070"]]

View map again

[[image:image-20230308115701-3.png||height="571" width="1085"]]

623

624

625

== 2.8 Datalog Feature ==

626

627

628

total 273 entries,by default,

629

630

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

635

636

637

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

== 2.9 Alarm Mode ==

(((

User can push the (% style="color:red" %)**RED button**(%%) by more than 5 seconds to enter Alarm Mode. Alarm Mode is used to send SOS info to IoT platform.

)))

(((

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

655

)))

656

657

* Server sends a downlink command to exit.

658

* User fast press the RED button 10 times.

659

660

(((

661

When exit alarm mode, (% style="color:red" %)**RED LED**(%%) will light up for 5 seconds, indicating that the alarm mode is exited. And the alert flag will be set to false.

)))

== 2.10 Transport Mode ==

666

667

668

In Transport Mode, TrackerD will check if there is motion (threldhold defined by **[[PT)>>||anchor="H3.2.16GetorSetThresholdformotiondetectFF08Sincefirmware1.4.3FF09"]]** . If there is no motion, device will send uplinks every 20 minutes (Defined by **[[TDC)>>||anchor="H3.2.1SetTransmitInterval"]]** . If there is motion, device will send uplink every 5 minutes(defined by **[[MTDC)>>||anchor="H3.2.3SetTransportModePackettransmissioninterval"]]**.

669

670

When device is set in Transport Mode, it will uplink more frequenctly during moving.

671

672

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

673

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

674

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

675

676

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

677

678

== 2.11 LED Status ==

679

680

681

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

682

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

683

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

684

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

685

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

686

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

687

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

688

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

689

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

690

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

691

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

692

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

693

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

694

695

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

696

697

== 2.12 Button Function ==

698

699

700

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

701

702

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

703

704

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

705

706

707

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

708

709

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

710

711

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

712

713

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

714

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

715

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

716

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

717

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

718

719

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

720

721

722

== 2.13 USB Port Function ==

723

724

725

The USB interface of TrackerD has below functions:

726

727

* Power on the device

728

* Recharge the battery

729

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

730

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

731

732

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

733

734

735

== 2.14 Sleep Mode ==

736

737

738

(% style="color:blue" %)**Sleep Mode:**(%%) To prevent accidental touch of the red button during transportation or assembly, so the peripherals of the device are turned off and enter deep sleep.

739

740

In SLEEP mode, you need to reset by (% style="color:#037691" %)**reset button**.

741

742

Use the** (% style="color:#4472c4" %)AT+SLEEP(%%)** command to put the device into sleep.

743

744

745

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

746

747

748

User can configure TrackerD via AT Command or LoRaWAN Downlink.

749

750

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

751

752

753

== 3.1 Access AT Command ==

754

755

756

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.

757

758

759

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

760

761

762

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:

763

764

765

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

766

767

768

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

769

770

771

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

772

773

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

774

775

== 3.2 Command Set ==

776

777

=== 3.2.1 Set Transmit Interval ===

778

779

780

Set device uplink interval.

781

782

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

783

784

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

785

786

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

787

788

789

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

790

791

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

792

793

794

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

795

796

797

Set alarm packet transmit interval

798

799

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

800

801

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

802

803

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

804

805

806

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

807

808

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

809

810

811

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

812

813

814

Set Transport Mode packet transmit interval

815

816

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

817

818

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

819

820

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

821

822

823

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

824

825

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

826

827

828

=== 3.2.4 Exit Alarm ===

829

830

831

Server send downlink command to exit Alarm mode

832

833

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

834

835

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

836

837

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

838

839

840

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

841

842

843

Disable/Enable LED for position, downlink and uplink

844

845

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

846

847

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

848

849

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

850

851

852

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

853

854

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

855

856

857

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

858

859

860

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

861

862

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

863

864

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

865

866

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

867

868

869

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

870

871

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

872

873

874

=== 3.2.7 Set Positioning Mode ===

875

876

877

SMOD define how TrackerD scan and uplink data:

878

879

880

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

881

882

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

883

884

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

885

886

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

887

888

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

889

890

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

891

892

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

893

894

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

895

896

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

897

898

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

899

900

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

901

902

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

903

904

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

905

906

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

907

908

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

909

910

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

911

912

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

913

914

915

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

916

917

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

918

919

920

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

921

922

923

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.

924

925

926

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.

927

928

929

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

930

931

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

932

933

**Example:** AT+FTIME=150

934

935

936

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

937

938

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

939

940

941

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

942

943

944

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.

945

946

947

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

948

949

950

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

951

952

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

953

954

955

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

956

957

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

958

959

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

960

961

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

962

963

964

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

965

966

967

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

968

969

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

**~ Example:**

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

975

976

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

977

978

979

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

980

981

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

982

983

984

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

985

986

987

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.

988

989

990

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

991

992

The default factory setting is 0.

993

994

995

**Command Example Function Response:**

996

997

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

998

999

1000

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

1001

1002

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

1003

1004

1005

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

1006

1007

1008

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.

1009

1010

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

1011

1012

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

1013

1014

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

1015

1016

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

1017

1018

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

1019

1020

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

1021

1022

1023

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

1024

1025

1026

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.

1027

1028

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

1029

1030

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

1031

1032

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

1033

1034

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

1035

1036

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

1037

1038

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

1039

1040

1041

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

1042

1043

1044

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

1045

1046

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

1047

1048

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

1049

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

1050

1051

1052

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

1053

1054

1055

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

1056

1057

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

1058

1059

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

1060

1061

1062

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

1063

1064

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

1065

1066

1067

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

1068

1069

1070

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

1071

1072

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

1073

1074

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

Example:

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

1079

1080

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

1081

1082

1083

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

1084

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

1085

1086

1087

=== **3.2.17 Set AT command window time（Since firmware 1.4.5）** ===

1088

1089

AT command window time setting, customers can set the required time according to their own operation mode.The unit is second.

1090

1091

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

1092

1093

(% style="color:#037691" %)**AT+ATST=XX**

Example:

AT+ATST=15 ~-~-> Set the time to 15 seconds

1098

1099

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

1100

0xB5 0F ~/~/ Same as AT+ATST=15

1101

1102

=== **3.2.18 Set the stepmeter mode（Since firmware 1.4.5）** ===

1103

1104

After setting the step counting mode, it cannot be interrupted by motion. This mode is very power consuming. Used on some special occasions.

1105

1106

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

1107

1108

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

Example:

AT+PM=1 ~-~-> Turn on step counting mode

1113

1114

AT+PM=0 ~-~-> Turn OFF step counting mode

1115

1116

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

1117

0xB6 01 ~/~/ Same as AT+PM=1

1118

1119

1120

=== 3.2.19 Set down the decline detection mode（Since firmware 1.4.5） ===

1121

1122

This mode is used in conjunction with AT+PT(The recommended threshold is between 50 and 70, you need to set it according to the environment yourself). This function is used in hospitals, nursing homes, nursing homes and other places to prevent the elderly and patients from falling. No one knows.

1123

1124

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

1125

1126

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

Example:

AT+FD=1 ~-~-> Turn on the Fall detection

1131

1132

AT+FD=0 ~-~-> Turn OFF the Fall detection

1133

1134

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

1135

0xB7 01 ~/~/ Same as AT+FD=1

1136

1137

1138

= 4. Setting for Different Scenarios =

= 5. Upload Firmware =

1143

1144

== 5.1 Firmware Change Log ==

1145

1146

1147

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

1148

1149

1150

== 5.2 How to upgrade firmware ==

1151

1152

1153

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

1154

1155

1156

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

1157

1158

1159

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

1160

1161

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

1162

1163

1164

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

1165

1166

1167

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

1168

1169

1170

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

1171

1172

1173

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

1178

1179

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

1180

1181

1182

**Users need to use below files:**

boot_app0.bin @0e000

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

1187

1188

1189

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

After upgrade finish, it will show finish as below:

1194

1195

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

1196

1197

1198

= 6. Developer Guide =

1199

1200

== 6.1 Compile Source Code ==

1201

1202

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

1203

1204

1205

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

1206

1207

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

1208

1209

1210

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

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

1215

1216

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

1217

1218

1219

=== 6.1.2 Build the development environment ===

1220

1221

1222

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

1223

1224

[[https:~~/~~/www.arduino.cn/thread-5838-1-1.html>>url:https://links.jianshu.com/go?to=https%3A%2F%2Fwww.arduino.cn%2Fthread-5838-1-1.html]]

1225

1226

1227

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

1228

1229

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

1230

1231

1232

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

1233

1234

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

1235

1236

1237

Restart the IDE after the addition is complete, then:

1238

1239

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

1240

1241

1242

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

1243

1244

1245

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

1246

Don't quit halfway.~~! If you quit halfway, there is a high probability that it will freeze, and you will need to download again next time. (If you click to continue downloading, an error will be reported after completion)**

1247

1248

1249

Then enter a long waiting process. If you don't want to wait, you can go to the Internet to download directly, and then import:

1250

1251

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

1252

1253

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

1254

1255

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

1256

1257

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

1258

1259

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

1260

1261

1262

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

1263

1264

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

1265

1266

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

1267

1268

1269

Either way, in the end:

1270

1271

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

1272

1273

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

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

**~ Figure1**

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

**Figure2**

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

1289

1290

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

1291

1292

1293

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

1294

1295

1296

== 6.2 Source Code ==

1297

1298

1299

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

1300

1301

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

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

1306

1307

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

1312

1313

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

= 7. FAQ =

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

1319

1320

1321

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

1322

1323

1324

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

1325

1326

1327

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

(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:314px" %)

1332

|=(% style="width: 118px;background-color:#D9E2F3;color:#0070C0" %)**Pin**|=(% style="width: 67px;background-color:#D9E2F3;color:#0070C0" %)**Color**|=(% style="width: 123px;background-color:#D9E2F3;color:#0070C0" %)**USB Pin**

1333

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

1334

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

1335

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

1336

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

1337

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

1338

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

1339

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

1340

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

1341

1342

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

1343

1344

1345

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

1346

1347

=== 7.3.1 Serial port utility ===

1348

1349

1350

Serial port utility requires you to automatically add data streams.

1351

1352

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

1353

1354

(% class="wikigeneratedid" %)

1355

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

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

1360

1361

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

1362

1363

1364

=== 7.3.2 SecureCRT ===

1365

1366

1367

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.

1368

1369

1370

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

1371

1372

1373

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

=== 7.3.3 PUTTY ===

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

1380

1381

1382

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.

1383

1384

1385

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

1386

1387

1388

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

1389

1390

1391

(% class="box infomessage" %)

1392

(((

1393

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

1394

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

1395

)))

1396

1397

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

1398

1399

1400

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

1405

1406

1407

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

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

1412

1413

1414

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

1419

1420

1421

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

1422

1423

1424

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

1425

1426

1427

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

1428

1429

1430

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

1431

1432

1433

== 7.6 Can alert mode and transport mode be used together? ==

1434

1435

1436

Yes, you can also press the panic button to sound the alarm if set to transport mode

1437

1438

1439

= 8 Trouble Shooting =

1440

1441

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

1458

1459

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

1470

1471

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

)))

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

1476

1477

1478

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

1479

1480

1481

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

1482

1483

1484

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

1485

1486

1487

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

1488

1489

1490

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

1491

1492

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

**Figure 2**

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

1498

1499

1500

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

1501

1502

After the upgrade is completed, enter (% style="color:blue" %)**AT+CFG**(%%) as shown in the figure below.

1503

1504

1505

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

1506

1507

1508

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.

1509

1510

After AT+FDR. please set

1511

1512

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

1513

1514

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

**Example:**

AT+PDOP=7.00

AT+FTIME=180

AT+DEUI=70B3D57ED0053981

1523

1524

AT+APPEUI=D23345667BCBCCAF

1525

1526

AT+APPKEY=F402A1A7A350445A7CD2DEA95511BFA1

1527

1528

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

1529

1530

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

1531

1532

AT+APPSKEY=dacce2299ecd97a73ee3f80b5a46a559 ( no need for OTAA)

1533

1534

1535

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

1536

1537

1538

Please download version 1.4.2 again

1539

1540

1541

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

1542

1543

1544

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

1545

1546

2) Set PDOP to a higher value.

1547

1548

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

1549

1550

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

1551

1552

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

1553

1554

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

1555

1556

1557

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

1558

1559

1560

When upgrading, use the erase button to upgrade

1561

1562

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

1563

1564

1565

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

1566

1567

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

1568

1569

1570

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

1571

1572

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

1573

1574

1575

Reboot information after upgrade

1576

1577

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

1578

1579

1580

Use (% style="color:blue" %)**AT+FDR**(%%) command to reset and then use (% style="color:blue" %)**AT+CFG**(%%) to check whether the configuration is back to normal

1581

1582

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

1583

1584

1585

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

1586

1587

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

1588

1589

1590

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

1591

1592

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

1593

1594

1595

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

1596

1597

1598

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

1599

1600

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

= 9. Order Info =

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

1607

1608

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

1609

1610

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

1611

1612

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

1613

1614

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

1615

1616

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

1617

1618

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

1619

1620

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

1621

1622

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

1623

1624

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

= 10. Packing Info =

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

1630

1631

* TrackerD LoRaWAN GPS/BLE Tracker x 1

1632

1633

* USB recharge & program cable x 1

1634

1635

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

1636

1637

* Device Size: 85 x 48 x 15 mm

* Weight: 50g

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

= 11. Support =

* Support is provided Monday to Friday, from 09:00 to 18:00 GMT+8. Due to different timezones we cannot offer live support. However, your questions will be answered as soon as possible in the before-mentioned schedule.

1647

1648

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

1655

1656

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

1657