TS01-CB -- NB-IoT/LTE-M Tilting Sensor User Manual

The Dragino TS01-CB is a (% style="color:blue" %)**NB-IoT/LTE-M Tilting Sensor**(%%) for Internet of Things solution. TS01-CB is an outdoor Tilting Sensor specially designed for (% style="color:blue" %)**detecting the angle of trees, buildings or large scale equipment**.

26

27

TS01-CB measures pitch and roll angle and converts to NB-IoT wireless data and sends to IoT platform via NB-IoT/CAT-M1 network.

28

29

TS01-CB supports different uplink methods including (% style="color:blue" %)**MQTT, MQTTs, UDP , TCP or CoAP **(%%)for different application requirement, and support uplinks to various IoT Servers.

30

31

TS01-CB (% style="color:blue" %)**supports BLE configure **(%%)and(% style="color:blue" %)** OTA update**(%%) which make user easy to use.

32

33

TS01-CB is powered by (% style="color:blue" %)**8500mAh Li-SOCI2 battery**(%%), it is designed for long-term use up to several years.

34

35

TS01-CB has optional built-in SIM card and default IoT server connection version. Which makes it works with simple configuration.

== 1.2 Features ==

* For -NB Bands: B1/B2/B3/B4/B5/B8/B12/B13/B17/B18/B19/B20/B25/B28/B66/B70/B85

42

* For -CB Bands: B1/B2/B3/B4/B5/B8/B12/B13~/~/B18/B19/B20/B25/B28/B66/B71/B85

43

* CAT-M1 / LTE-M Bands: B1/B2/B3/B4/B5/B8/B12/B13/B18/B19/B20/B25/B26/B27/B28/B66/B85

44

* Ultra-low power consumption

45

* Detect pitch and roll angle

46

* Support Angle Alarm

47

* Support Datalog feature

48

* Multiply Sampling and one uplink

49

* GNSS for Location Report

50

* Support BLE remote configure and update firmware

51

* Uplink on periodically

52

* Downlink to change configure

53

* 8500mAh Battery for long term use

54

* Uplink via MQTT, MQTTs, TCP, UDP or CoAP

55

* Nano SIM card slot for NB-IoT SIM

56

57

== 1.3 Specification ==

58

59

60

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

61

62

* Supply Voltage: 2.6v ~~ 3.6v

63

* Operating Temperature: -40 ~~ 85°C

64

65

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

66

67

* Measure Pitch and Roll

68

* Accuracy: 0.3°C

69

70

(% style="color:blue" %)**NB-IoT Spec:**

71

72

(% style="color:#037691" %)**NB-IoT Module: BG95-NGFF**

73

74

(% style="color:#037691" %)**Support Bands:**

* B1 @H-FDD: 2100MHz

* B2 @H-FDD: 1900MHz

* B3 @H-FDD: 1800MHz

* B4 @H-FDD: 2100MHz

* B5 @H-FDD: 860MHz

* B8 @H-FDD: 900MHz

* B12 @H-FDD: 720MHz

* B13 @H-FDD: 740MHz

* B17 @H-FDD: 730MHz

* B18 @H-FDD: 870MHz

* B19 @H-FDD: 870MHz

* B20 @H-FDD: 790MHz

* B25 @H-FDD: 1900MHz

89

* B28 @H-FDD: 750MHz

90

* B66 @H-FDD: 2000MHz

91

* B70 @H-FDD: 2000MHz

92

* B85 @H-FDD: 700MHz

93

94

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

95

96

* Li/SOCI2 un-chargeable battery

97

* Capacity: 8500mAh

98

* Self Discharge: <1% / Year @ 25°C

99

* Max continuously current: 130mA

100

* Max boost current: 2A, 1 second

101

102

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

103

104

* STOP Mode: 10uA @ 3.3v

105

* Max transmit power: 350mA@3.3v

106

107

== 1.4 Sleep mode and working mode ==

108

109

110

(% style="color:blue" %)**Deep Sleep Mode: **(%%)Sensor doesn't have any NB-IoT activate. This mode is used for storage and shipping to save battery life.

111

112

(% style="color:blue" %)**Working Mode:** (%%)In this mode, Sensor will work as NB-IoT Sensor to Join NB-IoT network and send out sensor data to server. Between each sampling/tx/rx periodically, sensor will be in IDLE mode), in IDLE mode, sensor has the same power consumption as Deep Sleep mode.

113

114

115

== 1.5 Button & LEDs ==

116

117

118

[[image:Main.User Manual for LoRaWAN End Nodes.D20-LBD22-LBD23-LB_LoRaWAN_Temperature_Sensor_User_Manual.WebHome@1675071855856-879.png]]

119

120

121

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

122

|=(% style="width: 167px;background-color:#4F81BD;color:white" %)**Behavior on ACT**|=(% style="width: 117px;background-color:#4F81BD;color:white" %)**Function**|=(% style="width:226px;background-color:#4F81BD;color:white" %)**Action**

123

|(% style="width:167px" %)Pressing ACT between 1s < time < 3s|(% style="width:117px" %)Send an uplink|(% style="width:225px" %)(((

124

If sensor has already attached to NB-IoT network, sensor will send an uplink packet, (% style="color:blue" %)**blue led** (%%)will blink once.

125

Meanwhile, BLE module will be active and user can connect via BLE to configure device.

126

)))

127

|(% style="width:167px" %)Pressing ACT for more than 3s|(% style="width:117px" %)Active Device|(% style="width:225px" %)(((

128

(% style="color:green" %)**Green led**(%%) will fast blink 5 times, device will enter (% style="color:#037691" %)**OTA mode**(%%) for 3 seconds. And then start to attach NB-IoT network.

129

(% style="color:green" %)**Green led**(%%) will solidly turn on for 5 seconds after joined in network.

130

Once sensor is active, BLE module will be active and user can connect via BLE to configure device, no matter if device attach NB-IoT network or not.

131

)))

132

|(% style="width:167px" %)Fast press ACT 5 times.|(% style="width:117px" %)Deactivate Device|(% style="width:225px" %)(% style="color:red" %)**Red led**(%%) will solid on for 5 seconds. Means device is in Deep Sleep Mode.

133

134

(% style="color:red" %)**Note: When the device is executing a program, the buttons may become invalid. It is best to press the buttons after the device has completed the program execution.**

135

136

137

== 1.6 BLE connection ==

138

139

140

TS01-CB support BLE remote configure and firmware update.

141

142

143

BLE can be used to configure the parameter of sensor or see the console output from sensor. BLE will be only activate on below case:

144

145

* Press button to send an uplink

146

* Press button to active device.

147

* Device Power on or reset.

148

149

If there is no activity connection on BLE in 60 seconds, sensor will shut down BLE module to enter low power mode.

150

151

152

== 1.7 Pin Definitions , Switch & SIM Direction ==

153

154

155

TS01-CB use the mother board which as below.

156

157

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

158

159

160

=== 1.7.1 Jumper JP2 ===

161

162

163

Power on Device when put this jumper.

164

165

166

=== 1.7.2 BOOT MODE / SW1 ===

167

168

169

**1)** (% style="color:blue" %)**ISP**(%%): upgrade mode, device won't have any signal in this mode. but ready for upgrade firmware. LED won't work. Firmware won't run.

170

171

**2)** (% style="color:blue" %)**Flash**(%%): work mode, device starts to work and send out console output for further debug

172

173

174

=== 1.7.3 Reset Button ===

175

176

177

Press to reboot the device.

178

179

180

=== 1.7.4 SIM Card Direction ===

181

182

183

See this link. [[How to insert SIM Card>>url:http://wiki.dragino.com/xwiki/bin/view/Main/General%20Configure%20to%20Connect%20to%20IoT%20server%20for%20-NB%20%26%20-NS%20NB-IoT%20models/#H2.AttachNetwork]].

184

185

186

== 1.8 Sketch of Pitch and Roll ==

187

188

189

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

190

191

192

== 1.9 Installation direction ==

193

194

195

(% style="color:blue" %)**Horizontal installation:**

196

197

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

198

199

(% style="color:blue" %)**Vertical installation:**

200

201

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

202

203

204

= 2. Use TS01-CB to communicate with IoT Server =

205

206

== 2.1 Send data to IoT server via NB-IoT network ==

207

208

209

The TS01-CB is equipped with a NB-IoT module, the pre-loaded firmware in TS01-CB will get environment data from sensors and send the value to local NB-IoT network via the NB-IoT module. The NB-IoT network will forward this value to IoT server via the protocol defined by TS01-CB.

210

211

212

Below shows the network structure:

213

214

[[image:image-20240720155858-1.jpeg]]

215

216

217

There are two version: (% style="color:blue" %)**-GE**(%%) and (% style="color:blue" %)**-1T**(%%) version of TS01-CB.

218

219

220

(% style="color:blue" %)**GE Version**(%%): This version doesn't include SIM card or point to any IoT server. User needs to use AT Commands to configure below two steps to set TS01-CB send data to IoT server.

221

222

* Install NB-IoT SIM card and configure APN. See instruction of [[Attach Network>>url:http://wiki.dragino.com/xwiki/bin/view/Main/General%20Configure%20to%20Connect%20to%20IoT%20server%20for%20-NB%20%26%20-NS%20NB-IoT%20models/#H2.AttachNetwork]].

223

224

* Set up sensor to point to IoT Server. See instruction of [[Configure to Connect Different Servers>>url:http://wiki.dragino.com/xwiki/bin/view/Main/General%20Configure%20to%20Connect%20to%20IoT%20server%20for%20-NB%20%26%20-NS%20NB-IoT%20models/#H3.Configuretoconnecttodifferentservers]].

225

226

Below shows result of different server as a glance.

227

228

(% border="1" cellspacing="4" style="width:515px" %)

229

|(% style="background-color:#4f81bd; color:white; width:100px" %)**Servers**|(% style="background-color:#4f81bd; color:white; width:300px" %)**Dash Board**|(% style="background-color:#4f81bd; color:white; width:115px" %)**Comments**

230

|(% style="width:127px" %)[[Node-Red>>url:http://wiki.dragino.com/xwiki/bin/view/Main/General%20Configure%20to%20Connect%20to%20IoT%20server%20for%20-NB%20%26%20-NS%20NB-IoT%20models/#H3.5A0Node-RedA028viaA0MQTT29]]|(% style="width:385px" %)(((

231

(% style="text-align:center" %)

232

[[image:image-20230819113244-8.png||height="183" width="367"]]

233

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

234

|(% style="width:127px" %)[[DataCake>>url:http://wiki.dragino.com/xwiki/bin/view/Main/General%20Configure%20to%20Connect%20to%20IoT%20server%20for%20-NB%20%26%20-NS%20NB-IoT%20models/#H3.4Datacake]]|(% style="width:385px" %)(((

235

(% style="text-align:center" %)

236

[[image:image-20230819113244-9.png||height="119" width="367"]]

237

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

238

|(% style="width:127px" %)[[Tago.IO>>url:http://wiki.dragino.com/xwiki/bin/view/Main/General%20Configure%20to%20Connect%20to%20IoT%20server%20for%20-NB%20%26%20-NS%20NB-IoT%20models/#H3.7A0Tago.ioA028viaA0MQTT29]]|(% style="width:385px" %) |(% style="width:170px" %)

239

|(% style="width:127px" %)[[General UDP>>url:http://wiki.dragino.com/xwiki/bin/view/Main/General%20Configure%20to%20Connect%20to%20IoT%20server%20for%20-NB%20%26%20-NS%20NB-IoT%20models/#H3.1GeneralA0UDPA0Connection]]|(% style="width:385px" %)Raw Payload. Need Developer to design Dash Board|(% style="width:170px" %)

240

|(% style="width:127px" %)[[General MQTT>>url:http://wiki.dragino.com/xwiki/bin/view/Main/General%20Configure%20to%20Connect%20to%20IoT%20server%20for%20-NB%20%26%20-NS%20NB-IoT%20models/#H3.2GeneralA0MQTTA0Connection]]|(% style="width:385px" %)Raw Payload. Need Developer to design Dash Board|(% style="width:170px" %)

241

|(% style="width:127px" %)[[ThingSpeak>>url:http://wiki.dragino.com/xwiki/bin/view/Main/General%20Configure%20to%20Connect%20to%20IoT%20server%20for%20-NB%20%26%20-NS%20NB-IoT%20models/#H3.3A0ThingSpeakA028viaA0MQTT29]]|(% style="width:385px" %)(((

242

(% style="text-align:center" %)

243

[[image:image-20230819113244-10.png||height="104" width="367"]]

244

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

245

|(% style="width:127px" %)[[ThingsBoard>>url:http://wiki.dragino.com/xwiki/bin/view/Main/General%20Configure%20to%20Connect%20to%20IoT%20server%20for%20-NB%20%26%20-NS%20NB-IoT%20models/#H3.6A0ThingsBoard.CloudA028viaA0MQTT29]]|(% style="width:385px" %)(((

246

(% style="text-align:center" %)

247

[[image:image-20230819113244-11.png||height="141" width="367"]]

248

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

249

250

(% style="color:blue" %)**1T Version**(%%): This version has 1NCE SIM card pre-installed and configure to send value to ThingsEye. User Just need to select the sensor type in ThingsEyeand Activate TS01-CB and user will be able to see data in ThingsEye. See here for [[ThingsEye Config Instruction>>url:https://wiki.thingseye.io/xwiki/bin/view/Main/]].

251

252

253

== 2.2 Payload Types ==

254

255

256

To meet different server requirement, TS01-CB supports different payload type.

**Includes:**

* [[General JSON format payload>>||anchor="H2.2.1GeneralJsonFormat28Type3D529"]]. (Type=5)

261

262

* [[HEX format Payload>>||anchor="H2.2.2HEXformatPayload28Type3D029"]]. (Type=0)

263

264

* [[ThingSpeak Format>>||anchor="H2.2.4ThingSpeakPayload28Type3D129"]]. (Type=1)

265

266

* [[ThingsBoard Format>>||anchor="H2.2.3ThingsBoardPayload28Type3D329"]]. (Type=3)

267

268

User can specify the payload type when choose the connection protocol. Example:

269

270

(% style="color:#037691" %)**AT+PRO=1,0** (%%) ~/~/ Use COAP Connection & hex Payload

271

272

(% style="color:#037691" %)**AT+PRO=1,5** (%%) ~/~/ Use COAP Connection & Json Payload

273

274

(% style="color:#037691" %)**AT+PRO=2,0** (%%) ~/~/ Use UDP Connection & hex Payload

275

276

(% style="color:#037691" %)**AT+PRO=2,5** (%%) ~/~/ Use UDP Connection & Json Payload

277

278

(% style="color:#037691" %)**AT+PRO=3,0** (%%) ~/~/ Use MQTT Connection & hex Payload

279

280

(% style="color:#037691" %)**AT+PRO=3,1 **(%%)~/~/ Use MQTT Connection & ThingSpeak

281

282

(% style="color:#037691" %)**AT+PRO=3,3 **(%%)~/~/ Use MQTT Connection & ThingsBoard

283

284

(% style="color:#037691" %)**AT+PRO=3,5 ** (%%) ~/~/ Use MQTT Connection & Json Payload

285

286

(% style="color:#037691" %)**AT+PRO=4,0** (%%) ~/~/ Use TCP Connection & hex Payload

287

288

(% style="color:#037691" %)**AT+PRO=4,5** (%%) ~/~/ Use TCP Connection & Json Payload

289

290

291

=== 2.2.1 General Json Format(Type~=5) ===

292

293

294

This is the General Json Format. As below:

295

296

(% style="color:#4472c4" %)**{"IMEI":"862406079145617","IMSI":"454312901015182","Model":"TS01-CB","temperature":21.9,"roll":71.03,"pitch":14.88,"interrupt":0,"interrupt_level":0,"battery":3.15,"signal":19,"time":"2024-12-19T02:33:34Z","latitude":0.000000,"longitude":0.000000,"gps_time":"1970-01-01T00:00:00Z","1":[409.5,0.00,0.00,"2024-12-19T02:09:12Z"],"2":[0.0,1.41,0.00,"2024-12-19T01:11:40Z"],"3":[0.0,1.41,0.00,"2024-12-19T00:56:40Z"],"4":[0.0,1.41,0.00,"2024-12-19T00:41:40Z"],"5":[0.0,1.41,0.00,"2024-12-19T00:26:40Z"],"6":[0.0,1.41,0.00,"2024-12-19T00:11:40Z"],"7":[0.0,1.41,0.00,"2024-12-18T23:56:40Z"],"8":[0.0,1.41,0.00,"2024-12-18T23:41:40Z"]}**

297

298

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

299

300

(% style="color:red" %)**Notice, from above payload:**

301

302

* Temperature, Roll, Pitch, Interrupt, Interrupt_level, Battery, Signal, time, Latitude, Longitude & GPS_Time are the value at uplink time.

303

304

* Json entry 1 ~~ 8 are the last 1 ~~ 8 sampling data as specify by (% style="color:#037691" %)**AT+CLOCKLOG=1,65535,15,8 ** (%%)Command. Each entry includes (from left to right): Temperature, Roll, Pitch, Sampling time.

305

306

=== 2.2.2 HEX format Payload(Type~=0) ===

307

308

309

This is the HEX Format. As below:

310

311

(% style="color:#4472c4" %)**f862406079145617f454312901015182026e0c8d19010000000000df1caa0900676386a900000000000000000000000000db23640ca36763862c0fff0000000067638048000001000000676372cc00000100000067636f4800000100000067636bc400000100000067636840000001000000676364bc00000100000067636138**

312

313

[[image:image-20241226100308-1.png||height="276" width="1794"]]

314

315

316

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

317

318

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

319

320

These bytes include the hardware and software version.

321

322

(% style="color:#037691" %)**Higher byte:**(%%) Specify Sensor Model: 0x02 for TS01-CB

323

324

(% style="color:#037691" %)**Lower byte:**(%%) Specify the software version: 0x6e=110, means firmware version 1.1.0

325

326

327

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

328

329

Sensor Battery Level.

Ex1: 0x0b45 = 2885mV

Ex2: 0x0dce = 3534mV

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

337

338

Read:0x(00)=0 (% style="color:#037691" %) (%%) ~/~/ horizontal direction

339

340

Read:0x(01)=1 (% style="color:#037691" %) (%%) ~/~/ Vertical direction

341

342

343

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

344

345

payload: 0x00 **~-~->** Alarm packet

346

347

payload: 0x01 **~-~->** Normal packet

348

349

350

(% style="color:blue" %)**Level of PA4:**

351

352

payload: 0x00 **~-~->** The PA4 is low level.

353

354

payload: 0x01 **~-~->** The PA4 is high level.

355

356

357

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

358

359

This data field shows if this packet is generated by interrupt or not.

**Example:**

If byte[0]&0x01=0x00 : Normal uplink packet.

364

365

If byte[0]&0x01=0x01 : Interrupt Uplink Packet.

366

367

368

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

369

370

This byte shows whether the interrupt is triggered by a high or low level.

371

372

**Ex1:** 0x00 Interrupt triggered by falling edge (low level)

373

374

**Ex2: **0x01 Interrupt triggered by rising edge (high level)

375

376

377

(% style="color:blue" %)**DS18B20 Temperature:**

**Example**:

If payload is: 0105H: (0105 & 8000 == 0), temp = 0105H /10 = 26.1 degree

382

383

If payload is: FF3FH : (FF3F & 8000 == 1) , temp = (FF3FH - 65536)/10 = -19.3 degrees.

384

385

(FF3F & 8000：Judge whether the highest bit is 1, when the highest bit is 1, it is negative)

386

387

If payload is: FFFF(H): (FFFF & 8000 == 1), Fixed display temp = -409.5℃, Indicates that there is no temperature data at this point in time or the built-in temperature chip does not detect the temperature or exceeds the detection range.

388

389

390

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

391

392

Read:0x(019C)=412 Value: 412 / 100=4.12

393

394

395

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

396

397

Read:0x(0251)=593 Value: 593/ 100=5.93

398

399

400

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

401

402

**Example: **0x015a7886(H)=22706310(D)=22.706150

403

404

405

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

406

407

**Example: **0x06cf341e(H)=114242590(D)=114.242830

408

409

410

(% style="color:blue" %)**TimeStamp/GPS_Timestamp: **

411

412

Unit TimeStamp Example: 64e2d74f(H) = 1692587855(D)

413

414

Put the decimal value into this link([[https:~~/~~/www.epochconverter.com)>>https://www.epochconverter.com]])to get the time.

415

416

417

=== 2.2.3 ThingsBoard Payload(Type~=3) ===

418

419

420

Type3 payload special design for ThingsBoard, it will also configure other default server to ThingsBoard.

421

422

(% style="color:#4472c4" %)**{

423

"topic": "002_CB",

424

"payload": {

425

"IMEI": "862406079145617",

426

"IMSI": "454312901015182",

"Model": "TS01-CB",

"temperature": 21.6,

"roll": 30.01,

"pitch": 2.91,

"interrupt": 0,

"interrupt_level": 0,

433

"battery": 3.17,

434

"signal": 23,

435

"time": "2024-12-19T06:52:56Z",

436

"latitude": 0.0,

437

"longitude": 0.0,

438

"gps_time": "1970-01-01T00:00:00Z",

439

"1": [21.5, -0.41, 0.1, "2024-12-19T05:49:26Z"],

440

"2": [20.5, -0.25, 0.02, "2024-12-19T05:34:26Z"],

441

"3": [20.5, -0.31, 0.02, "2024-12-19T05:19:26Z"],

442

"4": [20.7, -0.32, 0.01, "2024-12-19T05:04:26Z"],

443

"5": [20.8, -0.32, -0.03, "2024-12-19T04:49:26Z"],

444

"6": [21.1, -0.33, -0.02, "2024-12-19T04:34:26Z"],

445

"7": [21.3, -0.27, -0.02, "2024-12-19T04:19:26Z"],

446

"8": [21.7, -0.27, -0.02, "2024-12-19T04:04:26Z"]

}

}**

[[image:image-20250102105124-3.png||height="572" width="1269"]]

451

452

453

=== 2.2.4 ThingSpeak Payload(Type~=1) ===

454

455

456

This payload meets ThingSpeak platform requirement. It includes only five fields. Form 1~~5 are:

457

458

Temperature, Roll, Pitch, Battery & Signal. This payload type only valid for ThingsSpeak Platform

As below:

(% style="color:blue" %)**field1=Temperature value&field2=Roll value&field3=Pitch value&field4=Battery value&field5=Signal value**

463

464

[[image:image-20240709152047-5.png||height="568" width="853"]]

465

466

[[image:image-20240709152102-6.png||height="589" width="856"]]

467

468

469

= 3. Configure TS01-CB =

470

471

== 3.1 Configure Methods ==

472

473

474

TS01-CB supports below configure method:

475

476

* AT Command via Bluetooth Connection (**Recommended**): [[BLE Configure Instruction>>http://wiki.dragino.com/xwiki/bin/view/Main/BLE%20Bluetooth%20Remote%20Configure/]].

477

478

* AT Command via UART Connection : See [[UART Connection>>http://wiki.dragino.com/xwiki/bin/view/Main/UART%20Access%20for%20LoRa%20ST%20v4%20base%20model/#H2.3UARTConnectionforSN50v3basemotherboard]].

479

480

== 3.2 Serial Access Password ==

481

482

483

After the Bluetooth or UART connection is successful, use the Serial Access Password to enter the AT command window.

484

485

The label on the box of the node will print the initial password: AT+PIN=**xxxxxx**, and directly use the six-digit password to access the AT instruction window.

486

487

[[image:https://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/RS485-NB%2C-NS_RS485%2CUART_to_NB-IoT_Converter_User_Manual/WebHome/image-20250226165815-1.png?rev=1.1||alt="image-20250226165815-1.png"]]

488

489

490

If you need to change the password, use **AT+PWORD=**xxxxxx (6 characters), CB nodes only support lowercase letters.

491

492

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

493

494

495

(% style="color:red" %)**Note: After entering the command, you need to add a line break, and you can also set automatic line breaks in the Bluetooth tool or UART connection tool.**

496

497

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

498

499

== 3.3 AT Commands Set ==

500

501

502

AT+<CMD>? : Help on <CMD>

AT+<CMD> : Run <CMD>

AT+<CMD>=<value> : Set the value

507

508

AT+<CMD>=? : Get the value

509

510

511

(% style="color:blue" %)**General Commands**

AT : Attention

AT? : Short Help

AT+MODEL : Get module information

518

519

ATZ : Trig a reset of the MCU

520

521

AT+CFGMOD : Working mode selection

522

523

AT+DEUI : Get or set the Device ID

524

525

AT+CFG : Print all settings

526

527

AT+SERVADDR: Get or Set the Server address

528

529

AT+TDC : Get or set the application data transmission interval in s

530

531

AT+INTMOD : Get or Set the trigger interrupt mode (0:input, 1:falling or rising, 2:falling, 3:rising)

532

533

AT+APN : Get or set the APN

534

535

AT+5VT : Get or Set extend the time of 5V power

536

537

AT+PRO : Get or Set usage agreement (1:COAP,2:UDP,3:MQTT,4:TCP)

538

539

AT+RXDL : Get or Set the receiving time

540

541

AT+XALARM :ALARM MOD 1:Get or Set alarm of angle X(0-360) ALARM MOD 2: X(-180-180)

542

543

AT+YALARM :ALARM MOD 1:Get or Set alarm of angle Y(0-360) ALARM MOD 2: Y(-180-180)

544

545

AT+INSTAL:Get or Set the installation direction

546

547

AT+CAL:Angle calibration

548

549

AT+AMOD:Get or Set the alarm mode

550

551

AT+GETSENSORVALUE : Returns the current sensor measurement

552

553

AT+DNSCFG : Get or Set DNS Server

554

555

AT+CSQTIME : Get or Set the time to join the network

556

557

AT+GDNS : Get or Set the DNS

558

559

AT+TLSMOD : Get or Set the TLS mode

560

561

AT+SLEEP : Get or Set the sleep mode

562

563

AT+DEBUG : Entering/exiting debugging mode

564

565

AT+MQOS : Set the QoS level of MQTT

566

567

AT+IPTYPE : Set the IPv4 or IPv6

568

569

AT+QSW : Power on and power off BG95 module

570

571

AT+GETLOG : Print serial port logs

572

573

AT+CLOCKLOG: Get or set SHT record time

574

575

AT+QBAND: Get or set Frequency Band

576

577

AT+IOTMOD: Configure Network Category to be Searched for under LTE RAT

578

579

580

(% style="color:blue" %)**MQTT Management**

581

582

AT+CLIENT : Get or Set the MQTT clientID

583

584

AT+UNAME : Get or Set the MQTT Username

585

586

AT+PWD : Get or Set the MQTT password

587

588

AT+PUBTOPIC: Get or set MQTT publishing topic

589

590

AT+SUBTOPIC: Get or set MQTT subscription topic

591

592

593

(% style="color:blue" %)**Coap Management**

594

595

AT+URI1: Get or set CoAP option 1

596

597

AT+URI2: Get or set CoAP option 2

598

599

AT+URI3: Get or set CoAP option 3

600

601

AT+URI4: Get or set CoAP option 4

602

603

AT+URI5: Get or set CoAP option 5

604

605

AT+URI6: Get or set CoAP option 6

606

607

AT+URI7: Get or set CoAP option 7

608

609

AT+URI8: Get or set CoAP option 8

610

611

612

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

613

614

AT+GNSST : Extend the time to turn on GNSS

615

616

AT+GPS : Turn off and on GPS

617

618

AT+GTDC : Get or set GPS positioning interval in units of h

619

620

621

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

622

623

AT+FDR1 : Reset parameters to factory default values except for passwords

624

625

AT+FDR : Reset Parameters to Factory Default

626

627

AT+PWORD : Get or set the System password

628

629

AT+LDATA : Get the last upload data

630

631

AT+CDP : Read or Clear cached data

632

633

634

== 3.4 Test Uplink and Change Update Interval ==

635

636

637

By default, Sensor will send uplinks **every 2 hours.**

638

639

User can use below commands to change the uplink interval.

640

641

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

642

643

Example: AT+TDC=7200 ~/~/ Set Update Interval to 7200 seconds

644

645

(% style="color:blue" %)**Downlink Commands: **(% style="color:#037691" %)**0x01**

646

647

Format: Command Code (0x01) followed by 3 bytes.

648

649

Example: 12 hours= 43200 seconds 43200(D)=0xA8C0(H)

650

651

Downlink Payload: **01 00 A8 C0** ~/~/ AT+TDC=43200, Set Update Interval to 12 hours.

652

653

(% style="color:red" %)**Note: User can also push the button for more than 1 seconds to activate an uplink.**

654

655

656

== 3.5 Set the receiving time ==

657

658

659

Feature: Extend the receiving time

660

661

(% style="color:blue" %)**AT Command: **(% style="color:#037691" %)**AT+RXDL**

662

663

Example: AT+RXDL=1000 ~/~/ Set the receiving time delay to 1000ms

664

665

(% style="color:blue" %)**Downlink Commands: **(% style="color:#037691" %)**0x03**

666

667

Format: Command Code (0x03) followed by 3 bytes.

668

669

Example: Downlink Payload: **03 00 03 E8 **~/~/ AT+RXDL=1000

== 3.6 Reset ==

Feature: Trig a reset of the MCU.

676

677

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

678

679

(% style="color:blue" %)**Downlink Commands: **(% style="color:#037691" %)**0x04FF**

== 3.7 +5V ==

Feature: Set extend the time of 5V power.

686

687

(% style="color:blue" %)**AT Command: **(% style="color:#037691" %)**AT+5VT**

688

689

Example: AT+5VT=2000 ~/~/ Set extend the time of 5V power to 2000 ms

690

691

(% style="color:blue" %)**Downlink Commands: **(% style="color:#037691" %)**0x05**

692

693

Format: Command Code (0x05) followed by 3 bytes.

694

695

Example: Downlink Payload: **05 00 07 D0 **~/~/ AT+5VT=2000

696

697

698

== 3.8 Trigger an uplink by external interrupt ==

699

700

701

TS01-CB has an external trigger interrupt function. Users can use the PB15 pin to trigger the upload of data packets.

702

703

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

704

705

* (% style="color:#037691" %)**AT+INTMOD **(%%) ~/~/ Set the trigger interrupt mode

706

707

* (% style="color:#037691" %)**AT+INTMOD=0 **(%%) ~/~/ Disable Interrupt

708

709

* (% style="color:#037691" %)**AT+INTMOD=1 **(%%) ~/~/ Trigger by rising and falling edge

710

711

* (% style="color:#037691" %)**AT+INTMOD=2 **(%%) ~/~/ Trigger by falling edge

712

713

* (% style="color:#037691" %)**AT+INTMOD=3 **(%%) ~/~/ Trigger by rising edge

714

715

(% style="color:blue" %)**Downlink Commands: **(% style="color:#037691" %)**0x06**

716

717

Format: Command Code (0x06) followed by 3 bytes.

718

719

Example1: Downlink Payload: **06 00 00 01 **~/~/ AT+INTMOD=1

720

721

Example2: Downlink Payload: **06 00 00 03 **~/~/ AT+INTMOD=3

722

723

724

== 3.9 Set the QoS level ==

725

726

727

This command is used to set the QoS level of **MQTT**.

728

729

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

730

731

* (% style="color:#037691" %)**AT+MQOS=xx**(%%)** **~/~/ 0~~2

732

733

(% style="color:blue" %)**Downlink command:**(%%)** (% style="color:#037691" %)0x07(%%)**

734

735

Format: Command Code (0x07) followed by 1 byte.

736

737

**Ex1:** Downlink payload: **0x0700** ~/~/ AT+MQOS=0

738

739

**Ex2:** Downlink payload: **0x0701** ~/~/ AT+MQOS=1

740

741

742

== 3.10 Clock logging ==

743

744

745

Sometimes when we deploy lots of end nodes in field. We want all sensors sample data at the same time, and upload these data together for analyze. In such case, we can use clock loging feature.

746

747

We can use this command to set the start time of data recording and the time interval to meet the requirements of the specific collection time of data.

748

749

(% style="color:blue" %)**AT command:**(%%)** (% style="color:#037691" %)AT+CLOCKLOG=a,b,c,d(%%)**

750

751

(% style="color:#037691" %)**a: **(%%)**0:** Disable Clock logging. ** 1: **Enable Clock Logging

752

753

(% style="color:#037691" %)**b:**(%%)** **Specify First sampling start second: range **(0 ~~ 3599, 65535) ** ~/~/ (% style="color:red" %)**Note: **(%%)If parameter b is set to 65535, the log period starts after the node accesses the network and sends packets.

754

755

(% style="color:#037691" %)**c: **(%%)Specify the sampling interval: range **(0 ~~ 255 minutes)**

756

757

(% style="color:#037691" %)**d:**(%%)** **How many entries should be uplink on every TDC **(max 32)**

758

759

(% style="color:red" %)**Note: To disable clock recording, set the following parameters: AT+CLOCKLOG=1,65535,0,0**

760

761

[[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/SPH01-NB_NB-IoT_Soil_pH_Sensor_User_Manual/WebHome/image-20240315141254-1.png?rev=1.1||alt="image-20240315141254-1.png"]]

**Example:**

**AT+CLOCKLOG=1,65535,1,5**

766

767

After the node sends the first packet, data is recorded to the memory at intervals of 1 minute. For each TDC uplink, the uplink load will include: battery information + the last 5 memory records (payload + timestamp).

768

769

[[image:image-20240709183914-9.png||height="535" width="1150"]]

770

771

772

(% class="wikigeneratedid" %)

773

(% style="color:red" %)**Note: Users need to synchronize the server time before configuring this command. If the server time is not synchronized before this command is configured, the command takes effect only after the node is reset.**

774

775

(% style="color:blue" %)**Downlink command:**(%%)** (% style="color:#037691" %)0x08(%%)**

776

777

Format: Command Code (0x08) followed by 5 bytes.

778

779

* **Example 1**: Downlink Payload:** 08 01 FFFF 0F 08** ~/~/ Set SHT record time: AT+CLOCKLOG=1,65535,15,8

780

* **Example 2**: Downlink Payload:** 08 01 04B0 0F 08** ~/~/ Set SHT record time: AT+CLOCKLOG=1,1200,15,8

781

782

(% style="color:red" %)**Note: When entering the downlink payload, there must be no Spaces between bytes.**

783

784

785

== 3.11 Set the TLS mode ==

786

787

788

Refer to this link ([[MQTT Connection to send data to Tago.io>>http://wiki.dragino.com/xwiki/bin/view/Main/General%20Manual%20for%20-CB%20%2C%20-CS%20models/#H3.7Tago.io28viaMQTT29]])to use the TLS mode.

789

790

(% style="color:blue" %)**AT Command: **(% style="color:#037691" %)**AT+TLSMOD**

791

792

**Example 1: ** AT+TLSMOD=0,0 ~/~/ Disable TLS Mode.

793

794

**Example 2:** AT+TLSMOD=1,0 ~/~/ No authentication

795

796

AT+TLSMOD=1,1 ~/~/ Perform server authentication

797

798

AT+TLSMOD=1,2 ~/~/ Perform server and client authentication if requested by the remote server

799

800

(% style="color:blue" %)**Downlink command:**(%%)** (% style="color:#037691" %)0x09(%%)**

801

802

Format: Command Code (0x09) followed by 2 bytes.

803

804

Example1: Downlink Payload: **09 00 00 **~/~/ AT+TLSMOD=0,0

805

806

Example2: Downlink Payload: **09 01 02 **~/~/ AT+TLSMOD=1,2

807

808

809

== 3.12 Set GNSS open time ==

810

811

812

Extend the time to turn on GNSS. The automatic GPS location time is extended when the node is activated.

813

814

(% style="color:blue" %)**AT Command: **(% style="color:#037691" %)**AT+GNSST**

815

816

Example: AT+GNSST=30 ~/~/ Set the GPS positioning time to 30 seconds

817

818

(% style="color:blue" %)**Downlink command:**(%%)** (% style="color:#037691" %)0x10(%%)**

819

820

Format: Command Code (0x10) followed by 2 bytes.

821

822

Example: Downlink Payload: **10 00 1E **~/~/ AT+GNSST=30

823

824

825

== 3.13 Turn on/off GPS ==

826

827

828

(% style="color:blue" %)**AT Command: **(% style="color:#037691" %)**AT+GPS **

829

830

**Ex1: **AT+GPS=0 ~/~/ Turn off GPS

831

832

**Ex2: **AT+GPS=1 ~/~/ Turn on GPS

833

834

(% style="color:blue" %)**Downlink command:**(%%)** (% style="color:#037691" %)0x11(%%)**

835

836

Format: Command Code (0x11) followed by 1 byte.

837

838

Example: Downlink Payload: **11 01 **~/~/ AT+GPS=1

839

840

841

== 3.14 Set GPS positioning interval ==

842

843

844

Feature: Set GPS positioning interval (unit: hour).

845

846

When GPS is enabled, the node automatically locates and uplinks each time it passes **GTDC time** after activation.

847

848

(% style="color:blue" %)**AT Command: **(% style="color:#037691" %)**AT+GTDC**

849

850

Example: AT+GTDC=24 ~/~/ Set the GPS positioning interval to 24h.

851

852

(% style="color:blue" %)**Downlink command:**(%%)** (% style="color:#037691" %)0x12(%%)**

853

854

Format: Command Code (0x12) followed by 3 bytes.

855

856

Example: 24 hours: 24(D)=0x18(H)

857

858

Downlink Payload: **12 00 00 18 **~/~/ AT+GTDC=24

859

860

861

== 3.15 Set the search network time ==

862

863

864

Feature: Get or Set the time to join the network(unit: minutes).

865

866

(% style="color:blue" %)**AT Command: **(% style="color:#037691" %)**AT+CSQTIME**

867

868

Example: AT+CSQTIME=10 ~/~/ Set the search time to 10 minutes.

869

870

(% style="color:blue" %)**Downlink command:**(%%)** (% style="color:#037691" %)0x13(%%)**

871

872

Format: Command Code (0x13) followed by 1 byte.

873

874

Example: Downlink Payload: **13 0A **~/~/ AT+CSQTIME=10

== 3.16 Angle Alarm Feature ==

879

880

881

TS01-CB work flow with Alarm feature.

882

883

=== 3.16.1 Set the alarm mode ===

884

885

886

(% style="color:blue" %)**AT Command: **(% style="color:#037691" %)**AT+AMOD**

887

888

Ex1: AT+AMOD=0 ~/~/ Turn off alarm function.

889

890

Ex2: AT+AMOD=1 ~/~/ Set the alarm mode 1.

891

892

893

(% style="color:blue" %)**Downlink command:**(%%)** (% style="color:#037691" %)0x0B(%%)**

894

895

Format: Command Code (0x0B) followed by 1 byte.

896

897

Example: Downlink Payload: **0B 01 **~/~/ AT+AMOD=1

898

899

900

=== 3.16.2 Set alarm of angle X/Y ===

901

902

903

(% style="color:blue" %)**AT Command: **(% style="color:#037691" %)**AT+XALARM, AT+YALARM**

904

905

(% style="color:blue" %)**Downlink command:**(%%)** (% style="color:#037691" %)0x0A(%%)**(Command Code)

906

907

908

(% style="color:red" %)**TS01-CB has two alarm modes, XALARM and YALARM have different Settings according to different AMOD.**

909

910

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

911

912

(% style="color:#037691" %)**AT+AMOD=1 **(%%)~/~/ Downlink payload:** 0x0B 01**

913

914

(% style="color:#037691" %)**AT+XALARM=Xvalue, AT+YALARM=Yvalue **(%%)**(Value range: 0~~360)**

915

916

Format for (% style="color:#037691" %)**downlink command**(%%): **Command Code (0x0A) followed by 4 bytes**, the first two bytes are XALARM values, and the last two bytes are YALARM values.

917

918

When an angle change is detected that exceeds the range compared to the last time, an alarm is reported.

**For example:**

AT+AMOD=1 ~/~/ Downlink payload:** 0x0B 01**

923

924

AT+XALARM=10 AT+YALARM=20 ~/~/ 10(D)=0x0A(H), 20(D)=14(H), Downlink payload:** 0x0A 00 0A 00 14**

925

926

The last angle measured on the X-axis was 120 degrees, and this time the angle measured on the X-axis is 135 degrees, an alarm will be triggered to upload a data packet.

927

928

The last time the angle measured on the Y-axis was 100 degrees, but this time the angle measured on the Y-axis is 50 degrees, which will trigger an alarm and upload the data packet.

929

930

If the alarm conditions are met on the X-axis or Y-axis, an alarm will be triggered.

931

932

933

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

934

935

(% style="color:#037691" %)**AT+AMOD=2 **(%%)~/~/ Downlink payload:** 0x0B 02**

936

937

(% style="color:#037691" %)**AT+XALARM=min,max **(%%)**(Value range: -180~~180)**

938

939

When min=0, and max=0, The alarm in the X direction is disabled

940

941

When min=0, and max≠0, Alarm higher than max

942

943

When min≠0, and max=0, Alarm lower than min

944

945

When min≠0 and max≠0, Alarm higher than max or lower than min

946

947

(% style="color:#037691" %)**AT+YALARM=min,max **(%%)**(Value range:-180~~180)**

948

949

When min=0, and max=0, The alarm in the Y direction is disabled

950

951

When min=0, and max≠0, Alarm higher than max

952

953

When min≠0, and max=0, Alarm lower than min

954

955

When min≠0 and max≠0, Alarm higher than max or lower than min

956

957

958

In Alarm Mode 2, the XALARM and YALARM downlink instructions are still the same, as explained below:

959

960

(% style="color:#037691" %)**~-~->Downlink command: 0x0A**

961

962

Format: Command Code (**0x0A) followed by 8 bytes**.The first 4 bytes are the minimum and maximum values of XALARM, and the last 4 bytes are the minimum and maximum values of YALARM.

**Example 1:**

AT+AMOD=2 ~/~/ Downlink payload:** 0x0B 02**

967

968

AT+ XALARM=50,80 AT+YALARM=0,0 ~/~/ Downlink payload: **0X0A 00 32 00 50 00 00 00 00**

**Example 2:**

AT+AMOD=2 ~/~/ Downlink payload:** 0x0B 02**

973

974

AT+ XALARM=0,0 AT+ YALARM=20,30 ~/~/ Downlink payload: **0X0A 00 00 00 00 00 14 00 1E**

975

976

977

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

978

979

AT+AMOD=0 ~/~/ Turn off alarm function

980

981

982

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

983

984

(% style="color:#037691" %)**AT+CLOCKLOG=1,65535,15,8** (%%) ~/~/ The alarm interval is consistent with the detection interval of the clock recording function. It means triggering an alarm every 15 minutes.

985

986

987

== 3.17 Calibration and installation direction ==

988

989

990

Feature: Angle calibration.

991

992

(% style="color:blue" %)**AT+CAL : Calibration angle**

993

994

When the calibration angle is 0 or close to 0, it is considered successful calibration.

995

996

997

Before calibrating with (% style="color:blue" %)**AT+CAL**(%%) you need to check the mounting orientation of the angle module.

998

999

(% style="color:blue" %)**Installation direction command:**

1000

1001

(% style="color:#037691" %)**AT+INSTAL=0 ** (%%) ~/~/ Angle module in horizontal direction

1002

1003

(% style="color:#037691" %)**AT+INSTAL=1 ** (%%) ~/~/ Angle module in vertical direction

1004

1005

1006

**The position of the Angle module in the node:**

1007

1008

[[image:image-20241219102330-1.jpeg]]

1009

1010

(% style="color:red" %)**NOTE: The Angle module is located at the bottom of the node, and when the node is perpendicular to the ground and the antenna is facing down, the Angle module is in the correct horizontal direction.

1011

When the back of the node is parallel to the ground, the Angle module is in the correct vertical direction. If the direction is incorrect, it may result in opposite angles or inaccurate degrees.**

1012

1013

1014

After calibrating the node using (% style="color:#037691" %)**AT+INSTAL**(%%) and (% style="color:#037691" %)**AT+CAL,**(%%) we can use AT+ACC to calculate the current acceleration of each axis, when the acceleration of X,Y,Z axis is 0,0,1, it means correct calibration.

**Example: **

[[image:https://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/TS01-LB_LoRaWAN_Titling_Sensor_User_Manual/WebHome/image-20240919144954-2.png?width=764&height=602&rev=1.1||alt="image-20240919144954-2.png"]]

1019

1020

(% style="color:red" %)**NOTE: Regardless of whether the angle module is in the horizontal or vertical direction, it is correctly calibrated only when AX=0,AY=0,AZ=1(Two decimal places, with deviations), otherwise an error in angle measurement may occur during subsequent use.**

== 3.18 Set the IPv4 or IPv6 ==

1025

1026

1027

This command is used to set IP version.

1028

1029

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

1030

1031

* (% style="color:#037691; font-weight:bold" %)**AT+IPTYPE**(% style="color:#037691" %)**=1**(%%)** **~/~/ IPv4

1032

* (% style="color:#037691; font-weight:bold" %)**AT+IPTYPE**(% style="color:#037691" %)**=2**(%%)** **~/~/ IPv6

1033

1034

== 3.19 Configure Network Category to be Searched for under LTE RAT. ==

1035

1036

1037

(% style="color:blue" %)**AT command:**(%%)** (% style="color:#037691" %)AT+IOTMOD=xx(%%)**

1038

1039

(% style="color:#037691" %)**xx:**(%%) **0:** eMTC

**1:** NB-IoT

**2:** eMTC and NB-IoT

1044

1045

1046

== 3.20 Factory data reset ==

1047

1048

1049

Two different restore factory Settings configurations.

1050

1051

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

1052

1053

* (% style="color:#037691; font-weight:bold" %)**AT+FDR**(%%)** **~/~/ Reset Parameters to Factory Default.

1054

* (% style="color:#037691; font-weight:bold" %)**AT+FDR1**(%%)** **~/~/ Reset parameters to factory default values **except for passwords**.

1055

1056

== 3.21 Set CoAP option ==

1057

1058

1059

Feature: Set CoAP option, follow this link to set up the CoaP protocol.

1060

1061

(% style="color:blue" %)**AT command: **(% style="color:#037691; font-weight:bold" %)**AT+URI1~~AT+URI8**

1062

1063

(% style="color:#037691; font-weight:bold" %)**AT+URI1=11,"i" **(%%)~/~/ "i/" indicates that the endpoint supports observation mode. In -CB products, fixed setting AT+URI1=11,"i"

1064

1065

(% style="color:#037691; font-weight:bold" %)**AT+URI2=11,"CoAP endpoint URl" **(%%)~/~/ 11 is a fixed parameter.

1066

1067

**Example: ** i/13a35fbe-9515-6e55-36e8-081fb6aacf86

AT+URI1=11,"i"

AT+URI2=11,"13a35fbe-9515-6e55-36e8-081fb6aacf86"

1072

1073

~-~->If multiple groups of CoAP endpoint urls:

AT+URI3=11,"i"

AT+URI4=11,"CoAP endpoint URl"

1078

1079

1080

== 3.22 Power on / power off BG95 module ==

1081

1082

1083

This command is used to power on and power off BG95 module.

1084

1085

* (% style="color:blue" %)**AT command: **(% style="color:#037691" %)**AT+QSW**

1086

1087

The module is powered on after the command is sent for the first time, and powered off after the command is sent again.

1088

1089

[[image:image-20240709184729-10.png||height="589" width="675"]]

1090

1091

1092

== 3.23 Example Query saved historical records ==

1093

1094

1095

* (% style="color:blue" %)**AT command:**(%%)** (% style="color:#037691" %)AT+CDP(%%)**

1096

1097

This command can be used to search the saved history, recording up to 32 groups of data, each group of historical data contains a maximum of 100 bytes.

1098

1099

(% class="wikigeneratedid" %)

1100

[[image:image-20240709183204-7.png||height="586" width="672"]]

1101

1102

1103

== 3.24 Uplink log query ==

1104

1105

1106

* (% style="color:blue" %)**AT command:**(%%)** (% style="color:#037691" %)AT+GETLOG(%%)**

1107

1108

This command can be used to query upstream logs of data packets.

1109

1110

[[image:image-20240709183635-8.png||height="579" width="667"]]

1111

1112

1113

== 3.25 Set the downlink debugging mode(Since firmware v1.1.0) ==

1114

1115

1116

Feature: Set the conversion between the standard version and 1T version downlinks.

1117

1118

(% style="color:blue" %)**AT command: AT+DOWNTE**

1119

1120

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

1121

|=(% style="width: 138px; background-color: rgb(79, 129, 189); color: white;" %)**Command Example**|=(% style="width: 143px; background-color: rgb(79, 129, 189); color: white;" %)**Function/Parameters**|=(% style="width: 229px; background-color: rgb(79, 129, 189); color: white;" %)**Response/Explanation**

1122

|(% style="width:134px" %)AT+DOWNTE=?|(% style="width:143px" %)Get current Settings|(% style="width:229px" %)(((

0,0 (default)

OK

)))

|(% colspan="1" rowspan="2" style="width:134px" %)(((

AT+DOWNTE=a,b

)))|(% style="width:143px" %)**a**: Set the conversion between the downlink of the standard version and 1T version|(% style="width:229px" %)(((

1133

**0**: Set the downlink of the standard version.

1134

**1**: Set the downlink of the 1T version(ThingsEye platform)

1135

)))

1136

|(% style="width:143px" %)**b**: Enable/Disable downlink debugging|(% style="width:229px" %)(((

1137

**0**: Disable downlink debugging mode.

1138

**1**: Enable downlink debugging mode, users can see the original downlink reception.

)))

**Example:**

* AT+DOWNTE=0,1 ~/~/ Set to standard version downlink, and enable downlink debugging.

1144

* AT+DOWNTE=1,1 ~/~/ Set to 1T version downlink, and enable downlink debugging.

1145

1146

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

1147

1148

No downlink commands for feature

1149

1150

1151

== 3.26 Domain name resolution settings(Since firmware v1.1.1) ==

1152

1153

1154

Feature: Set static DNS resolution IP address.

1155

1156

(% style="color:blue" %)**AT command: AT+BKDNS**

1157

1158

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

1159

|=(% style="width: 138px; background-color: rgb(79, 129, 189); color: white;" %)**Command Example**|=(% style="width: 143px; background-color: rgb(79, 129, 189); color: white;" %)**Function/Parameters**|=(% style="width: 229px; background-color: rgb(79, 129, 189); color: white;" %)**Response/Explanation**

1160

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

1161

AT+BKDNS=?

1162

)))|(% style="width:143px" %)Get current Settings|(% style="width:606px" %)(((

1,0,NULL (default)

OK

)))

|(% colspan="1" rowspan="3" style="width:134px" %)(((

AT+BKDNS=a,b,c

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

1175

**a**: Enable/Disable static DNS resolution.

1176

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

1177

**0:** Disable static DNS resolution

1178

1179

**1**: Enable static DNS resolution. The ip address will be saved after the domain name is resolved, if the next domain name resolution fails, the last saved ip address will be used.

1180

)))

1181

|(% style="width:143px" %)**b**: Meaningless.|(% style="width:606px" %)(((

1182

Set to **0**.

1183

)))

1184

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

1185

**c**: Set the IP address manually.

1186

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

1187

The format is the same as AT+SERVADDR.

1188

If domain name resolution fails, this ip address will be used directly, if domain name resolution succeeds, parameter c will be updated to the successfully resolved IP address.

)))

**Example:**

* AT+BKDNS=0,0,NULL ~/~/Disable static DNS resolution.

1194

* AT+BKDNS=1,0,NULL ~/~/ Enable static DNS resolution.

1195

* AT+BKDNS=1,0,3.69.98.183,1883 ~/~/Enable static DNS resolution, if domain name resolution succeeds, the node uses the ip address successfully resolved and saves it to parameter c. If the domain name resolution fails, use the manually set ip address: 3.69.98.183 for communication.

1196

1197

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

1198

1199

No downlink commands for feature.

1200

1201

1202

= 4. Battery & Power Consumption =

1203

1204

1205

TS01-CB use ER26500 + SPC1520 battery pack. See below link for detail information about the battery info and how to replace.

1206

1207

[[**Battery Info & Power Consumption Analyze**>>http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20calculate%20the%20battery%20life%20of%20Dragino%20sensors%3F/]] .

1208

1209

1210

= 5. Firmware update =

1211

1212

1213

User can change device firmware to::

1214

1215

* Update with new features.

* Fix bugs.

Firmware and changelog can be downloaded from : **[[Firmware download link>>https://www.dropbox.com/scl/fo/1mzflb9p9kx15btnc11gr/AFOWfl6YZ38d4DYXc-ooMFA/TS01-CB?dl=0&rlkey=ku98jt8u30coqy66saebai2co&subfolder_nav_tracking=1]]**

1220

1221

Methods to Update Firmware:

1222

1223

* (Recommended way) OTA firmware update via BLE: [[**Instruction**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/BLE_Firmware_Update_NB_Sensors_BC660K-GL/]].

1224

1225

* Update through UART TTL interface : **[[Instruction>>http://wiki.dragino.com/xwiki/bin/view/Main/UART_Access_for_NB_ST_BC660K-GL/#H4.2UpdateFirmware28Assumethedevicealreadyhaveabootloader29]]**.

= 6. FAQ =

== 6.1 How can I access the BG95-NGFF AT Commands? ==

1230

1231

1232

User can access to BG95-NGFF directly and send AT Commands.

1233

1234

[[See BG95-NGFF AT Command set>>https://www.dropbox.com/scl/fo/1mzflb9p9kx15btnc11gr/ALDWTvDjuVoXvDJuYWCRh5U/Vendor%20Datasheet/BG95?dl=0&rlkey=ku98jt8u30coqy66saebai2co&subfolder_nav_tracking=1

]]

== 6.2 General Manual for -CB , -CS models ==

1239

1240

Users can follow the instructions in this [[link>>url:http://wiki.dragino.com/xwiki/bin/view/Main/General%20Manual%20for%20-CB%20%2C%20-CS%20models/]] to see how to configure to connect to different servers.

= 7. Order Info =

Part Number: (% style="color:blue" %)**TS01-CB-XX**

1247

1248

(% style="color:red" %)**XX:**

1249

1250

* (% style="color:#037691" %)**GE**(%%): General version ( Exclude SIM card)

1251

1252

* (% style="color:#037691" %)**1T**(%%): with 1NCE* 10 years 500MB SIM card Pre-confgure to ThingsEye server

= 8. Packing Info =

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

1258

1259

* TS01-CB NB-IoT/LTE-M Tilting Sensor x 1

1260

1261

* External antenna x 1

1262

1263

(% style="color:#037691" %)**Dimension and weight**:

* Device Size: cm

* Device Weight: g

* Package Size / pcs : cm

* Weight / pcs : g

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

1277

1278

* 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.cc>>mailto:Support@dragino.cc]].

1279

1280

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

Wiki source code of TS01-CB -- NB-IoT/LTE-M Tilting Sensor User Manual

Applications

Navigation