TrackerD - LoRaWAN Tracker User Manual(Remove WiFi)

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

* Integrated SPI flash : 4 MB

* RAM: 448 KB

* EEPROM: 520 KB

* Clock Speed: 32Mhz

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

60

61

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

62

* Operating Temperature: -40 ~~ 60°C

63

64

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

65

66

* Frequency Range,

67

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

68

* 168 dB maximum link budget.

69

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

70

* +14 dBm high efficiency PA.

71

* Programmable bit rate up to 300 kbps.

72

* High sensitivity: down to -148 dBm.

73

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

74

* Excellent blocking immunity.

75

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

76

* Fully integrated synthesizer with a resolution of 61 Hz.

77

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

78

* Built-in bit synchronizer for clock recovery.

79

* Preamble detection.

80

* 127 dB Dynamic Range RSSI.

81

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

82

* Packet engine up to 256 bytes with CRC.

83

* LoRaWAN 1.0.3 Specification

84

85

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

86

87

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

88

89

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

90

91

* Sleeping Mode: 200uA

92

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

93

* Tracking: max: 38mA

94

95

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

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

== 1.4 Applications ==

122

123

124

* Logistics and Supply Chain Management

125

* Human tracking

126

127

(% style="display:none" %)

= 2. Use TrackerD =

== 2.1 How it works? ==

134

135

136

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

137

138

139

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

140

141

142

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.

143

144

145

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

146

147

148

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:

149

150

151

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

152

153

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

154

155

156

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

157

158

159

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

160

161

162

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

163

164

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

165

166

167

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

168

169

170

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

171

172

173

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

174

175

176

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

177

178

179

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

180

181

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

182

183

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

184

185

186

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

187

188

189

== 2.3 Positioning Mode(SMOD) ==

190

191

192

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

193

194

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

195

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

196

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

197

198

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

199

200

201

== 2.4 Uplink Payload ==

202

203

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

204

205

206

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.

207

208

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

209

210

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

211

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

212

213

214

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

215

216

217

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

218

219

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

220

221

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

222

223

(% style="color:#037691" %)**Frequency Band**:

0x01: EU868

0x02: US915

0x03: IN865

0x04: AU915

0x05: KZ865

0x06: RU864

0x07: AS923

0x08: AS923-1

0x09: AS923-2

0x0a: AS923-3

(% style="color:#037691" %)**Sub-Band:**(%%) value 0x00~~0x08(only forAU915,US915,Others are 0xFF)

246

247

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

248

249

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

250

251

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

252

253

254

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

255

256

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

257

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

258

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

259

260

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

261

262

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

263

264

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

265

266

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

267

268

269

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

270

271

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

272

273

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

274

275

276

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

277

278

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

279

280

281

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

282

283

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

284

285

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

286

287

(% style="display:none" %)

288

289

290

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

291

292

293

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,

294

295

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

296

297

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

298

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

299

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

300

301

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

302

303

304

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

305

306

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

307

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

308

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

309

310

(% style="display:none" %)

311

312

313

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

314

315

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

316

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

317

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

318

319

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

320

321

322

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

323

324

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

325

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

326

327

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

328

329

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.

330

331

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:

332

333

334

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

335

336

337

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

338

339

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

340

341

342

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

343

344

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

345

346

347

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

348

349

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

350

351

(((

352

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

353

)))

354

355

* > 4.0v : 80% ~~ 100%

356

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

357

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

358

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

359

* < 3.39v: 0~~20%

360

361

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

362

363

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

364

365

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

366

367

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

368

369

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

370

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

371

372

373

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

374

375

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

376

377

378

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

379

380

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

381

382

Enable/Disable LED activity for uplink

383

384

(((

385

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

)))

(((

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

)))

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

394

395

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

396

397

398

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

399

400

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

401

402

403

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

404

405

406

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)

407

408

409

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

410

411

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

412

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

413

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

414

415

(% class="wikigeneratedid" %)

416

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

417

418

419

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

420

421

422

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.

423

424

425

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

426

427

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

428

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

429

* 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

430

431

The payload is 15 bytes, as below.

432

433

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

434

|**Size(bytes)**|4|4|2|1|1|1|1|1

435

436

437

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

438

439

440

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

441

442

443

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.

444

445

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

446

447

448

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

449

450

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

451

iBeacon MAJOR

452

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

453

iBeacon MINOR

454

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

455

iBeacon Measured Power

456

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

457

iBeacon RSSI

458

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

459

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

460

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

461

462

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

463

464

465

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

466

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

467

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

468

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

469

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

470

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

471

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

472

473

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

474

475

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

476

477

478

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

479

480

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

481

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

482

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

483

484

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

485

486

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

487

488

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

489

490

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

491

492

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

=== 2.4.7 Uplink FPORT~=9, BLE Positioning with Multiple iBeacon(Since firmware 1.4.7) ===

497

498

TrackerD supports BLE scanning for indoor positioning. Users can set SMOD to BLE pure or GPS/BLE Hybrid, so TrackerD will scan up to 40 BLE iBeacons and send uplinks.

499

500

User can set [[(% class="wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink" %)**BLEMASK**>>path:#H3.2.11A0SetBLEMASKtofilterBLEiBeacon]](%%) so TrackerD will only search the iBeacons which have UUID that match the BLEMASK settings.

501

502

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

503

|**Size(bytes)**|2|2|1|…..|2|2|1|2|1

504

505

506

(% class="wikigeneratedid" id="H" %)

507

[[image:image-20231023103116-1.png||height="448" width="901"]]

508

509

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

510

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

511

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

512

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

513

514

(% class="wikigeneratedid" %)

515

**Note: This mode does not have a fixed decoder. Its decoder depends on the number of beacons and can be parsed according to the order of the payload.**

516

payload format: (Major + Minor+Rssi)+(Major + Minor+Rssi)+...(Maximum forty group)...+BAT+State

517

518

519

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

520

521

522

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

523

524

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

525

526

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

527

528

529

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

530

531

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

532

533

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

534

535

536

== 2.5 Integrate with Datacake ==

537

538

539

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.

540

541

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

542

543

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

544

545

546

== 2.6 Integrate with Tago ==

547

548

549

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.

550

551

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

552

553

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

554

555

556

== 2.7 Integrate with Node-red ==

557

558

559

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

560

561

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

562

563

564

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

565

566

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

567

568

569

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

570

571

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

572

573

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

574

575

576

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

3. Display the map

Enter the link to the map:

581

582

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

583

584

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

585

586

587

Hit all input in input stream

588

589

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

View map again

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

595

596

597

== 2.8 Datalog Feature ==

598

599

600

total 273 entries,by default,

601

602

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

607

608

609

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

626

)))

627

628

* Server sends a downlink command to exit.

629

* User fast press the RED button 10 times.

630

631

(((

632

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

637

638

639

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

640

641

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

642

643

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

644

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

645

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

646

647

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

648

649

== 2.11 LED Status ==

650

651

652

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

653

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

654

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

655

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

656

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

657

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

658

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

659

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

660

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

661

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

662

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

663

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

664

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

665

666

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

667

668

== 2.12 Button Function ==

669

670

671

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

672

673

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

674

675

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

676

677

678

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

679

680

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

681

682

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

683

684

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

685

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

686

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

687

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

688

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

689

690

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

691

692

== 2.13 USB Port Function ==

693

694

695

The USB interface of TrackerD has below functions:

696

697

* Power on the device

698

* Recharge the battery

699

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

700

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

701

702

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

703

704

== 2.14 Sleep Mode ==

705

706

707

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

708

709

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

710

711

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

712

713

714

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

715

716

717

User can configure TrackerD via AT Command or LoRaWAN Downlink.

718

719

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

720

721

722

== 3.1 Access AT Command ==

723

724

725

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.

726

727

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

728

729

730

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:

731

732

733

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

734

735

736

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

737

738

739

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

740

741

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

742

743

== 3.2 Command Set ==

744

745

=== 3.2.1 Set Transmit Interval ===

746

747

748

Set device uplink interval.

749

750

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

751

752

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

753

754

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

755

756

757

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

758

759

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

760

761

762

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

763

764

765

Set alarm packet transmit interval

766

767

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

768

769

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

770

771

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

772

773

774

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

775

776

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

777

778

779

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

780

781

782

Set Transport Mode packet transmit interval

783

784

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

785

786

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

787

788

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

789

790

791

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

792

793

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

794

795

796

=== 3.2.4 Exit Alarm ===

797

798

799

Server send downlink command to exit Alarm mode

800

801

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

802

803

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

804

805

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

806

807

808

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

809

810

811

Disable/Enable LED for position, downlink and uplink

812

813

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

814

815

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

816

817

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

818

819

820

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

821

822

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

823

824

825

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

826

827

828

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

829

830

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

831

832

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

833

834

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

835

836

837

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

838

839

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

840

841

842

=== 3.2.7 Set Positioning Mode ===

843

844

845

SMOD define how TrackerD scan and uplink data:

846

847

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

848

849

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

850

851

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

852

853

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

854

855

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

856

857

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

858

859

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

860

861

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

862

863

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

864

865

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

866

867

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

868

869

870

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

871

872

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

873

874

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

875

876

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

877

878

AT+SMOD=2,0,3 ~-~-> (iBeacon) (Major + Minor+Rssi)+(Major + Minor+Rssi)+...(Maximum forty group)...+BAT+State

879

880

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

881

882

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

883

884

885

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

886

887

888

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.

889

890

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.

891

892

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

893

894

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

895

896

**Example:** AT+FTIME=150

897

898

899

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

900

901

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

902

903

904

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

905

906

907

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.

908

909

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

910

911

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

912

913

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

914

915

916

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

917

918

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

919

920

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

921

922

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

923

924

925

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

926

927

928

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

929

930

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

**Example:**

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

936

937

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

938

939

940

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

941

942

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

943

944

945

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

946

947

948

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.

949

950

951

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

952

953

The default factory setting is 0.

954

955

956

**Command Example Function Response:**

957

958

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

959

960

961

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

962

963

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

964

965

966

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

967

968

969

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.

970

971

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

972

973

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

974

975

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

976

977

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

978

979

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

980

981

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

982

983

984

=== 3.2.13 Disable/Enable Information printing(Since firmware 1.4.1) ===

985

986

987

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

988

989

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

990

991

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

992

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

993

994

995

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

996

997

998

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

999

1000

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

1001

1002

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

1003

1004

1005

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

1006

1007

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

1008

1009

1010

=== 3.2.15 Get or Set Threshold for motion detect(Since firmware 1.4.3) ===

1011

1012

1013

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

1014

1015

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

1016

1017

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

Example:

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

1022

1023

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

1024

1025

1026

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

1027

1028

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

1029

1030

1031

=== 3.2.16 Set AT command window time(Since firmware 1.4.5) ===

1032

1033

1034

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

1035

1036

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

1037

1038

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

Example:

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

1043

1044

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

1045

1046

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

1047

1048

1049

=== 3.2.17 Set the stepmeter mode(Since firmware 1.4.5) ===

1050

1051

1052

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

1053

1054

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

1055

1056

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

Example:

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

1061

1062

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

1063

1064

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

1065

1066

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

1067

1068

1069

=== 3.2.18 Set down the decline detection mode(Since firmware 1.4.5) ===

1070

1071

1072

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.

1073

1074

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

1075

1076

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

**Example:**

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

1081

1082

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

1083

1084

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

1085

1086

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

1087

1088

1089

=== 3.2.19 Disable/Enable buzzer(Since firmware 1.4.6) ===

1090

1091

1092

Disable/Enable buzzer for Alarm, downlink and uplink

1093

1094

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

1095

1096

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

Example:

AT+BEEP=1 ~-~-> Turn on the buzzer

1101

1102

AT+BEEP=0 ~-~-> Turn OFF the buzzer

1103

1104

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

1105

1106

0xB9 01 ~/~/ Same as AT+BEEP=1

1107

1108

1109

=== 3.2.20 Set long press time(Since firmware 1.4.6) ===

1110

1111

1112

When using the red button Changan to alarm, press and hold the time to set 0~~10 seconds, which is convenient for use scenarios.

1113

1114

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

1115

1116

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

Example:

AT+EAT=2 ~-~-> Set the long press time to 2s

1121

1122

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

1123

1124

0xBA 02 ~/~/ Same as AT+EAT=2

1125

1126

1127

= 4. Upload Firmware =

1128

1129

== 4.1 Firmware Change Log ==

1130

1131

1132

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

1133

1134

1135

== 4.2 How to upgrade firmware ==

1136

1137

1138

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

1139

1140

1141

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

1142

1143

1144

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

1145

1146

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

1147

1148

1149

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

1150

1151

1152

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

1153

1154

1155

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

1156

1157

1158

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

1163

1164

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

1165

1166

1167

**Users need to use below files:**

boot_app0.bin @0e000

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

1172

1173

1174

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

After upgrade finish, it will show finish as below:

1179

1180

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

1181

1182

1183

= 5. Developer Guide =

1184

1185

== 5.1 Compile Source Code ==

1186

1187

=== 5.1.1 Set up ARDUINO compile environment ===

1188

1189

1190

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

1191

1192

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

1193

1194

1195

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

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

1200

1201

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

1202

1203

1204

=== 5.1.2 Build the development environment ===

1205

1206

1207

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

1208

1209

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

1210

1211

1212

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

1213

1214

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

1215

1216

1217

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

1218

1219

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

1220

1221

1222

Restart the IDE after the addition is complete, then:

1223

1224

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

1225

1226

1227

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

1228

1229

1230

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

1231

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

1232

1233

1234

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:

1235

1236

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

1237

1238

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

1239

1240

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

1241

1242

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

1243

1244

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

1245

1246

1247

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

1248

1249

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

1250

1251

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

1252

1253

1254

Either way, in the end:

1255

1256

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

1257

1258

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

1274

1275

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

1276

1277

1278

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

1279

1280

1281

== 5.2 Source Code ==

1282

1283

1284

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

1285

1286

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

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

1291

1292

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

1297

1298

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

= 6. FAQ =

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

1304

1305

1306

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

1307

1308

1309

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

1310

1311

1312

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

1313

1314

1315

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

1316

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

1317

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

1318

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

1319

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

1320

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

1321

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

1322

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

1323

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

1324

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

1325

1326

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

1327

1328

1329

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

1330

1331

=== 6.3.1 Serial port utility ===

1332

1333

1334

Serial port utility requires you to automatically add data streams.

1335

1336

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

1337

1338

(% class="wikigeneratedid" %)

1339

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

1340

1341

1342

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

1343

1344

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

1345

1346

1347

=== 6.3.2 SecureCRT ===

1348

1349

1350

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.

1351

1352

1353

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

1354

1355

1356

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

=== 6.3.3 PUTTY ===

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

1363

1364

1365

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.

1366

1367

1368

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

1369

1370

1371

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

1372

1373

1374

(% class="box infomessage" %)

1375

(((

1376

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

1377

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

1378

)))

1379

1380

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

1381

1382

1383

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

1388

1389

1390

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

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

1395

1396

1397

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

1402

1403

1404

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

1405

1406

1407

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

1408

1409

1410

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

1411

1412

1413

[[Operating instructions for BLE indoor positioning>>doc:Main.User Manual for LoRaWAN End Nodes.TrackerD.Example of BLE indoor positioning python.WebHome]]

1414

1415

1416

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

1417

1418

1419

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

1420

1421

1422

= 7 Trouble Shooting =

1423

1424

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

)))

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

)))

== 7.3 Problem after Upgrading Firmware ==

1441

1442

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

1453

1454

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

)))

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

1459

1460

1461

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

1462

1463

1464

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

1465

1466

1467

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

1468

1469

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

1470

1471

1472

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

1473

1474

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

**Figure 2**

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

1480

1481

1482

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

1483

1484

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

1485

1486

1487

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

1488

1489

1490

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.

1491

1492

After AT+FDR. please set

1493

1494

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

1495

1496

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

**Example:**

AT+PDOP=7.00

AT+FTIME=180

AT+DEUI=70B3D57ED0053981

1505

1506

AT+APPEUI=D23345667BCBCCAF

1507

1508

AT+APPKEY=F402A1A7A350445A7CD2DEA95511BFA1

1509

1510

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

1511

1512

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

1513

1514

AT+APPSKEY=dacce2299ecd97a73ee3f80b5a46a559 ( no need for OTAA)

1515

1516

1517

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

1518

1519

1520

Please download version 1.4.2 again

1521

1522

1523

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

1524

1525

1526

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

1527

1528

2) Set PDOP to a higher value.

1529

1530

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

1531

1532

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

1533

1534

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

1535

1536

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

1537

1538

1539

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

1540

1541

1542

When upgrading, use the erase button to upgrade

1543

1544

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

1545

1546

1547

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

1548

1549

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

1550

1551

1552

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

1553

1554

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

1555

1556

1557

Reboot information after upgrade

1558

1559

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

1560

1561

1562

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

1563

1564

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

1565

1566

1567

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

1568

1569

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

1570

1571

1572

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

1573

1574

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

1575

1576

1577

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

1578

1579

1580

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

1581

1582

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

1583

1584

1585

== 7.8 Why when using some serial consoles, only inputting the first string port console will return "error"? ==

1586

1587

1588

Need to enter the entire command at once, not a single character.

1589

User can open a command window or copy the entire command to the serial console.

= 8. Order Info =

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

1596

1597

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

1598

1599

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

1600

1601

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

1602

1603

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

1604

1605

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

1606

1607

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

1608

1609

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

1610

1611

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

1612

1613

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

= 9. Packing Info =

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

1619

1620

* TrackerD LoRaWAN GPS/BLE Tracker x 1

1621

1622

* USB recharge & program cable x 1

1623

1624

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

1625

1626

* Device Size: 85 x 48 x 15 mm

* Weight: 50g

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

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

1636

1637

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

1638

1639

(% style="display:none" %)

= 11. Reference =

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

1646