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

102

* ESP32 PICO D4

103

* SX1276/78 Wireless Chip

104

* Arduino IDE Compatible

105

* Open source hardware / software

106

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

107

* Built-in3 axis accelerometer (LIS3DH)

108

* Humidity / temperature sensor : GXCAS Technology GXHT3X

109

* Motion sensing capability

110

* Power Monitoring

111

* Charging circuit via USB port

112

* 1000mA Li-on Battery power

113

* Tri-color LED, Alarm button

114

* Datalog

115

116

(% style="display:none" %)

117

118

119

== 1.4 Applications ==

120

121

122

* Logistics and Supply Chain Management

123

* Human tracking

124

125

(% style="display:none" %)

= 2. Use TrackerD =

== 2.1 How it works? ==

131

132

133

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.

134

135

136

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

137

138

139

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.

140

141

142

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

147

148

149

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

150

151

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

152

153

154

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

155

156

157

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

158

159

160

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

161

162

163

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

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

168

169

170

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

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

175

176

177

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

182

183

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

184

185

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

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.

189

190

191

== 2.3 Positioning Mode(SMOD) ==

192

193

194

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

195

196

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

197

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

198

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

199

200

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

201

202

203

== 2.4 Uplink Payload ==

204

205

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

206

207

208

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.

209

210

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

211

212

213

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

214

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

215

216

217

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

218

219

220

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

221

222

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

223

224

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

225

226

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

249

250

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

251

252

253

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

254

255

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

256

257

258

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

259

260

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

261

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

262

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

263

264

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

265

266

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

267

268

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

269

270

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

271

272

273

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

274

275

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

276

277

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

278

279

280

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

281

282

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

283

284

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

285

286

287

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

288

289

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

290

291

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

292

293

(% style="display:none" %)

294

295

296

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

297

298

299

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,

300

301

302

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

303

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

**Size(bytes)**

2

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

308

2

309

)))

310

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

311

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

312

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

313

314

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

315

316

317

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

318

319

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

320

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

321

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

322

323

(% style="display:none" %)

324

325

326

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

327

328

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

329

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

330

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

331

332

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

333

334

335

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

336

337

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

338

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

339

340

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

341

342

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.

343

344

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:

345

346

347

[[image:1664502116362-706.png||_mstalt="293306"]]

348

349

350

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

351

352

[[image:1664502166010-515.png||_mstalt="291395"]]

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

357

358

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

359

360

361

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

362

363

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

364

365

(((

366

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

367

)))

368

369

* > 4.0v : 80% ~~ 100%

370

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

371

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

372

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

373

* < 3.39v: 0~~20%

374

375

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

376

377

378

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

416

417

418

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

419

420

421

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)

422

423

424

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

425

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

426

**Size(bytes)**

427

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

428

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

429

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

430

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

431

432

(% class="wikigeneratedid" %)

433

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

434

435

436

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

437

438

439

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.

440

441

442

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

443

444

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

445

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

446

* 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

447

448

The payload is 15 bytes, as below.

449

450

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

457

458

459

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

460

461

462

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.

463

464

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

465

466

467

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

468

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

469

**Size(bytes)**

470

471

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

472

iBeacon MAJOR

473

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

474

iBeacon MINOR

475

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

476

iBeacon Measured Power

477

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

478

iBeacon RSSI

479

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

480

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

481

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

482

483

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

484

485

486

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

487

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

488

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

489

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

490

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

491

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

492

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

493

494

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

495

496

497

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

498

499

500

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

501

502

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

503

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

504

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

505

506

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

507

508

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

509

510

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

511

512

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

513

514

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

515

516

517

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

518

519

520

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.

521

522

523

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

524

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

525

**Size(bytes)**

526

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

527

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

528

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

529

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

530

531

(% class="wikigeneratedid" %)

532

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

533

534

535

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

536

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

537

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

538

539

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

540

541

542

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

543

544

545

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

546

547

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

548

549

550

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

555

556

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

557

558

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

559

560

561

== 2.5 Integrate with Datacake ==

562

563

564

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.

565

566

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

567

568

569

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

570

571

572

== 2.6 Integrate with Tago ==

573

574

575

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.

576

577

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

578

579

580

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

581

582

583

== 2.7 Integrate with Node-red ==

584

585

586

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

587

588

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

589

590

591

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

592

593

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

594

595

596

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

597

598

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

599

600

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

601

602

603

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

3. Display the map

Enter the link to the map:

608

609

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

610

611

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

612

613

614

Hit all input in input stream

615

616

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

View map again

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

622

623

624

== 2.8 Datalog Feature ==

625

626

627

total 273 entries,by default,

628

629

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

634

635

636

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

654

)))

655

656

* Server sends a downlink command to exit.

657

* User fast press the RED button 10 times.

658

659

(((

660

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

665

666

667

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

668

669

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

670

671

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

672

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

673

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

674

675

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

676

677

== 2.11 LED Status ==

678

679

680

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

681

|=(% style="width: 150px;background-color:#D9E2F3;color:#0070C0" %)**Event**|=(% style="width: 200px;background-color:#D9E2F3;color:#0070C0" %)**Action**|=(% style="width: 150px;background-color:#D9E2F3;color:#0070C0" %)**AT+LON to control on/off**

682

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

683

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

684

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

685

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

686

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

687

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

688

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

689

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

690

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

691

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

692

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

693

694

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

695

696

== 2.12 Button Function ==

697

698

699

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

700

701

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

702

703

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

704

705

706

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

707

708

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

709

710

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

711

712

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

713

|=(% style="width: 100px;background-color:#D9E2F3;color:#0070C0" %)**Function**|=(% style="width: 205px;background-color:#D9E2F3;color:#0070C0" %)**Action**|=(% style="width: 205px;background-color:#D9E2F3;color:#0070C0" %)**Description**

714

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

715

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

716

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

717

718

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

719

720

== 2.13 USB Port Function ==

721

722

723

The USB interface of TrackerD has below functions:

724

725

* Power on the device

726

* Recharge the battery

727

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

728

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

729

730

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

731

732

== 2.14 Sleep Mode ==

733

734

735

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

736

737

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

738

739

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

740

741

742

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

743

744

745

User can configure TrackerD via AT Command or LoRaWAN Downlink.

746

747

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

748

749

750

== 3.1 Access AT Command ==

751

752

753

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.

754

755

756

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

757

758

759

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:

760

761

762

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

763

764

765

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

766

767

768

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

769

770

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

771

772

== 3.2 Command Set ==

773

774

=== 3.2.1 Set Transmit Interval ===

775

776

777

Set device uplink interval.

778

779

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

780

781

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

782

783

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

784

785

786

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

787

788

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

789

790

791

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

792

793

794

Set alarm packet transmit interval

795

796

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

797

798

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

799

800

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

801

802

803

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

804

805

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

806

807

808

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

809

810

811

Set Transport Mode packet transmit interval

812

813

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

814

815

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

816

817

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

818

819

820

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

821

822

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

823

824

825

=== 3.2.4 Exit Alarm ===

826

827

828

Server send downlink command to exit Alarm mode

829

830

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

831

832

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

833

834

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

835

836

837

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

838

839

840

Disable/Enable LED for position, downlink and uplink

841

842

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

843

844

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

845

846

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

847

848

849

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

850

851

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

852

853

854

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

855

856

857

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

858

859

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

860

861

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

862

863

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

864

865

866

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

867

868

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

869

870

871

=== 3.2.7 Set Positioning Mode ===

872

873

874

SMOD define how TrackerD scan and uplink data:

875

876

877

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

878

879

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

880

881

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

882

883

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

884

885

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

886

887

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

888

889

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

890

891

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

892

893

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

894

895

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

896

897

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

898

899

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

900

901

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

902

903

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

904

905

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

906

907

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

908

909

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

910

911

912

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

913

914

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

915

916

917

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

918

919

920

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.

921

922

923

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.

924

925

926

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

927

928

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

929

930

**Example:** AT+FTIME=150

931

932

933

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

934

935

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

936

937

938

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

939

940

941

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.

942

943

944

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

945

946

947

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

948

949

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

950

951

952

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

953

954

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

955

956

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

957

958

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

959

960

961

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

962

963

964

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

965

966

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

**~ Example:**

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

972

973

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

974

975

976

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

977

978

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

979

980

981

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

982

983

984

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.

985

986

987

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

988

989

The default factory setting is 0.

990

991

992

**Command Example Function Response:**

993

994

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

995

996

997

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

998

999

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

1000

1001

1002

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

1003

1004

1005

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.

1006

1007

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

1008

1009

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

1010

1011

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

1012

1013

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

1014

1015

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

1016

1017

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

1018

1019

1020

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

1021

1022

1023

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.

1024

1025

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

1026

1027

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

1028

1029

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

1030

1031

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

1032

1033

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

1034

1035

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

1036

1037

1038

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

1039

1040

1041

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

1042

1043

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

1044

1045

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

1046

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

1047

1048

1049

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

1050

1051

1052

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

1053

1054

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

1055

1056

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

1057

1058

1059

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

1060

1061

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

1062

1063

1064

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

1065

1066

1067

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

1068

1069

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

1070

1071

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

Example:

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

1076

1077

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

1078

1079

1080

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

1081

1082

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

1083

1084

1085

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

1086

1087

1088

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

1089

1090

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

1091

1092

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

Example:

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

1097

1098

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

1099

1100

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

1101

1102

1103

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

1104

1105

1106

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

1107

1108

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

1109

1110

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

Example:

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

1115

1116

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

1117

1118

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

1119

1120

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

1121

1122

1123

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

1124

1125

1126

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.

1127

1128

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

1129

1130

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

Example:

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

1135

1136

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

1137

1138

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

1139

1140

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

1141

1142

1143

= 4. Setting for Different Scenarios =

= 5. Upload Firmware =

1148

1149

== 5.1 Firmware Change Log ==

1150

1151

1152

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

1153

1154

1155

== 5.2 How to upgrade firmware ==

1156

1157

1158

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

1159

1160

1161

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

1162

1163

1164

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

1165

1166

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

1167

1168

1169

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

1170

1171

1172

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

1173

1174

1175

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

1176

1177

1178

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

1183

1184

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

1185

1186

1187

**Users need to use below files:**

boot_app0.bin @0e000

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

1192

1193

1194

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

After upgrade finish, it will show finish as below:

1199

1200

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

1201

1202

1203

= 6. Developer Guide =

1204

1205

== 6.1 Compile Source Code ==

1206

1207

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

1208

1209

1210

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

1211

1212

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

1213

1214

1215

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

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

1220

1221

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

1222

1223

1224

=== 6.1.2 Build the development environment ===

1225

1226

1227

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

1228

1229

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

1230

1231

1232

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

1233

1234

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

1235

1236

1237

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

1238

1239

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

1240

1241

1242

Restart the IDE after the addition is complete, then:

1243

1244

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

1245

1246

1247

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

1248

1249

1250

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

1251

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

1252

1253

1254

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:

1255

1256

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

1257

1258

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

1259

1260

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

1261

1262

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

1263

1264

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

1265

1266

1267

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

1268

1269

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

1270

1271

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

1272

1273

1274

Either way, in the end:

1275

1276

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

1277

1278

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

1294

1295

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

1296

1297

1298

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

1299

1300

1301

== 6.2 Source Code ==

1302

1303

1304

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

1305

1306

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

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

1311

1312

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

1317

1318

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

= 7. FAQ =

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

1324

1325

1326

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

1327

1328

1329

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

1330

1331

1332

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

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

1337

|=(% style="width: 120px;background-color:#D9E2F3;color:#0070C0" %)**Pin**|=(% style="width: 69px;background-color:#D9E2F3;color:#0070C0" %)**Color**|=(% style="width: 125px;background-color:#D9E2F3;color:#0070C0" %)**USB Pin**

1338

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

1339

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

1340

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

1341

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

1342

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

1343

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

1344

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

1345

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

1346

1347

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

1348

1349

1350

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

1351

1352

=== 7.3.1 Serial port utility ===

1353

1354

1355

Serial port utility requires you to automatically add data streams.

1356

1357

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

1358

1359

(% class="wikigeneratedid" %)

1360

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

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

1365

1366

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

1367

1368

1369

=== 7.3.2 SecureCRT ===

1370

1371

1372

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.

1373

1374

1375

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

1376

1377

1378

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

=== 7.3.3 PUTTY ===

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

1385

1386

1387

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.

1388

1389

1390

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

1391

1392

1393

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

1394

1395

1396

(% class="box infomessage" %)

1397

(((

1398

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

1399

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

1400

)))

1401

1402

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

1403

1404

1405

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

1410

1411

1412

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

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

1417

1418

1419

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

1424

1425

1426

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

1427

1428

1429

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

1430

1431

1432

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

1433

1434

1435

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

1436

1437

1438

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

1439

1440

1441

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

1442

1443

1444

= 8 Trouble Shooting =

1445

1446

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

1463

1464

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

1475

1476

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

)))

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

1481

1482

1483

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

1484

1485

1486

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

1487

1488

1489

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

1490

1491

1492

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

1493

1494

1495

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

1496

1497

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

**Figure 2**

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

1503

1504

1505

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

1506

1507

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

1508

1509

1510

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

1511

1512

1513

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.

1514

1515

After AT+FDR. please set

1516

1517

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

1518

1519

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

**Example:**

AT+PDOP=7.00

AT+FTIME=180

AT+DEUI=70B3D57ED0053981

1528

1529

AT+APPEUI=D23345667BCBCCAF

1530

1531

AT+APPKEY=F402A1A7A350445A7CD2DEA95511BFA1

1532

1533

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

1534

1535

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

1536

1537

AT+APPSKEY=dacce2299ecd97a73ee3f80b5a46a559 ( no need for OTAA)

1538

1539

1540

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

1541

1542

1543

Please download version 1.4.2 again

1544

1545

1546

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

1547

1548

1549

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

1550

1551

2) Set PDOP to a higher value.

1552

1553

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

1554

1555

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

1556

1557

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

1558

1559

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

1560

1561

1562

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

1563

1564

1565

When upgrading, use the erase button to upgrade

1566

1567

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

1568

1569

1570

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

1571

1572

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

1573

1574

1575

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

1576

1577

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

1578

1579

1580

Reboot information after upgrade

1581

1582

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

1583

1584

1585

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

1586

1587

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

1588

1589

1590

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

1591

1592

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

1593

1594

1595

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

1596

1597

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

1598

1599

1600

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

1601

1602

1603

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

1604

1605

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

1612

1613

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

1614

1615

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

1616

1617

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

1618

1619

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

1620

1621

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

1622

1623

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

1624

1625

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

1626

1627

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

1628

1629

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

= 10. Packing Info =

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

1635

1636

* TrackerD LoRaWAN GPS/BLE Tracker x 1

1637

1638

* USB recharge & program cable x 1

1639

1640

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

1641

1642

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

1652

1653

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

1654

1655

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

= 12. Reference =

* [[**Firmware in Bin format**>>https://www.dropbox.com/sh/733s8xlwahhqg1d/AABxDz80lBVX_to8zNuUQWFja?dl=0]]

1662