DS03A-NB -- NB-IoT Door Sensor User Manual

The Dragino DS03A-NB is a (% style="color:blue" %) **NB-IoT Door Sensor**(%%) for Internet of Things solution. It (% style="color:blue" %)**detects door open/close status**(%%) and uplinks to IoT server via NB-IoT network. user can see the door status, open duration, open counts in the IoT Server.

22

23

The DS03A-NB will send periodically data every 2 hours as well as for each door open/close action. It also counts the door open times and calculates the last door open duration. Users can also disable the uplink for each open/close event, instead, DS03A-NB can count each open event and uplink periodically.

24

25

DS03A-NB supports (% style="color:blue" %)**Datalog Feature,** (%%)it can save the data when there is no NB-IoT network and uplink when network recover.

26

27

DS03A-NB has the (% style="color:blue" %)**Open Alarm Feature**,(%%) user can set this feature so the device will send an alarm if the door has been open for a certain time.

28

29

DS03A-NB is designed for outdoor use. It has a weatherproof enclosure and industrial level battery to work in low to high temperatures

30

31

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

32

33

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

34

35

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

36

37

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

38

39

[[image:image-20231011093807-6.png||height="278" width="879"]]

== 1.2 Features ==

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

46

* Ultra-low power consumption

47

* Upload water flow volume

48

* Door Open/Close detect

49

* Door open/close statistics

50

* Datalog Feature

51

* Open Alarm Feature

52

* Multiply Sampling and one uplink

53

* Support Bluetooth v5.1 remote configure and update firmware

54

* Uplink on periodically

55

* Downlink to change configure

56

* 8500mAh Battery for long term use

57

* Nano SIM card slot for NB-IoT SIM

58

59

== 1.3 Specification ==

60

61

62

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

63

64

* Supply Voltage: 2.5v ~~ 3.6v

65

* Operating Temperature: -40 ~~ 85°C

66

67

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

68

69

(% style="color:#037691" %)**NB-IoT Module: BC660K-GL**

70

71

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

86

* B28 @H-FDD: 750MHz

87

* B66 @H-FDD: 2000MHz

88

* B70 @H-FDD: 2000MHz

89

* B85 @H-FDD: 700MHz

90

91

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

92

93

* Li/SOCI2 un-chargeable battery

94

* Capacity: 8500mAh

95

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

96

* Max continuously current: 130mA

97

* Max boost current: 2A, 1 second

98

99

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

100

101

* STOP Mode: 10uA @ 3.3v

102

* Max transmit power: 350mA@3.3v

103

104

(% class="wikigeneratedid" id="H1.4Ratedenvironmentalconditions" %)

105

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

106

107

108

== 1.4 Applications ==

109

110

111

[[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LDS03A%20-%20Outdoor%20LoRaWAN%20OpenClose%20Door%20Sensor%20Manual/WebHome/1654741400370-813.png?rev=1.1||alt="1654741400370-813.png"]]

112

113

114

== 1.5 Sleep mode and working mode ==

115

116

117

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

118

119

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

120

121

122

== 1.6 Button & LEDs ==

123

124

125

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

126

127

128

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

129

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

130

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

131

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

132

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

133

)))

134

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

135

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

136

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

137

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.

138

)))

139

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

140

141

== 1.7 BLE connection ==

142

143

144

DS03A-NB support BLE remote configure and firmware update.

145

146

147

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:

148

149

* Press button to send an uplink

150

* Press button to active device.

151

* Device Power on or reset.

152

153

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

154

155

156

== 1.8 Pin Definitions & Switch ==

157

158

159

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

160

161

162

=== 1.8.1 Jumper JP2 ===

163

164

165

Power on Device when put this jumper.

166

167

168

=== 1.8.2 BOOT MODE / SW1 ===

169

170

171

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

172

173

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

174

175

176

=== 1.8.3 Reset Button ===

177

178

179

Press to reboot the device.

180

181

(% style="display:none" %)

== 1.9 Mechanical ==

[[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/D20-LBD22-LBD23-LB_LoRaWAN_Temperature_Sensor_User_Manual/WebHome/1675143884058-338.png?rev=1.1||alt="1675143884058-338.png"]]

187

188

[[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/D20-LBD22-LBD23-LB_LoRaWAN_Temperature_Sensor_User_Manual/WebHome/1675143899218-599.png?rev=1.1||alt="1675143899218-599.png"]]

189

190

[[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/D20-LBD22-LBD23-LB_LoRaWAN_Temperature_Sensor_User_Manual/WebHome/1675143909447-639.png?rev=1.1||alt="1675143909447-639.png"]]

**Probe Mechanical:**

195

196

197

[[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LDS03A%20-%20Outdoor%20LoRaWAN%20OpenClose%20Door%20Sensor%20Manual/WebHome/1654741444887-479.png?width=513&height=399&rev=1.1||alt="1654741444887-479.png"]]

== 1.10 Magnet Distance ==

202

203

204

* Wood Door: 10mm ~~ 30mm

205

* Iron Door: 30 ~~ 45mm

= 2. Use DS03A-NB to communicate with IoT Server =

210

211

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

212

213

214

The DS03A-NB is equipped with a NB-IoT module, the pre-loaded firmware in DS03A-NB 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 DS03A-NB.

215

216

217

Below shows the network structure:

218

219

[[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/DS03A-NB_NB-IoT_Door_Sensor_User_Manual/WebHome/image-20231011093807-6.png?width=879&height=278&rev=1.1||alt="image-20231011093807-6.png"]]

220

221

222

There are two version: (% style="color:blue" %)**-GE**(%%) and (% style="color:blue" %)**-1D**(%%) version of DS03A-NB.

223

224

225

(% 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 DS03A-NB send data to IoT server.

226

227

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

228

229

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

230

231

Below shows result of different server as a glance.

232

233

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

234

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

235

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

236

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

237

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

238

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

239

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

240

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

241

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

242

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

243

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

244

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

245

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

246

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

247

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

248

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

249

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

250

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

251

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

252

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

253

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

254

255

(% style="color:blue" %)**1D Version**(%%): This version has 1NCE SIM card pre-installed and configure to send value to DataCake. User Just need to select the sensor type in DataCake and Activate DS03A-NB and user will be able to see data in DataCake. See here for [[DataCake Config Instruction>>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]].

256

257

258

== 2.2 Payload Types ==

259

260

261

To meet different server requirement, DS03A-NB supports different payload type.

**Includes:**

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

266

267

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

268

269

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

270

271

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

272

273

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

274

275

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

276

277

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

278

279

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

280

281

282

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

283

284

285

This is the General Json Format. As below:

286

287

(% style="color:#4472c4" %)**{"IMEI":"866207058378443","Model":"DS03A-NB","flow":217,"battery":3.54,"signal":24,"1":{221,2023/09/20 09:47:01},"2":{0,2023/09/20 09:15:04},"3":{0,2023/09/20 09:00:04},"4":{0,2023/09/20 08:45:03},"5":{0,2023/09/20 08:30:03},"6":{0,2023/09/20 08:15:03},"7":{0,2023/09/20 08:00:04},"8":{0,2023/09/20 07:45:04}}**

288

289

290

[[image:image-20230920175015-3.png||height="613" width="890"]]

291

292

293

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

294

295

* Distance , Battery & Signal are the value at uplink time.

296

297

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

298

299

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

300

301

302

This is the HEX Format. As below:

303

304

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

305

306

[[image:image-20230920172200-1.png||height="191" width="1047"]]

307

308

309

If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data.

310

311

[[image:image-20230920173352-2.png||height="636" width="919"]]

312

313

314

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

315

316

These bytes include the hardware and software version.

317

318

(% style="color:#037691" %)**Higher byte:**(%%) Specify Sensor Model: 0x12 for DS03A-NB

319

320

(% style="color:#037691" %)**Lower byte:**(%%) Specify the software version: 0x64=100, means firmware version 1.0.0

321

322

323

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

Ex1: 0x0dda = 3546mV

(% style="color:blue" %)**Signal Strength:**

329

330

NB-IoT Network signal Strength.

**Ex1: 0x15 = 21**

**0** -113dBm or less

**1** -111dBm

**2...30** -109dBm... -53dBm

339

340

**31** -51dBm or greater

341

342

**99** Not known or not detectable

343

344

345

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

346

347

Unit Timestamp Example: 650abc40(H) = 1695202368(D)

348

349

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

350

351

352

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

353

354

355

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

356

357

(% style="color:#4472c4" %)** {"IMEI": "866207058378443","Model": "DS03A","flow": 502,"battery": 3.57,"signal": 23}**

358

359

[[image:image-20230922094043-2.png||height="558" width="851"]]

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

364

365

366

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

367

368

Distance, Battery & Signal. This payload type only valid for ThingsSpeak Platform

As below:

(% style="color:#4472c4" %)**field1=Flow value&field2=Battery value&field3=Singal value**

373

374

[[image:image-20230921104741-1.png||height="565" width="826"]]

375

376

377

== 2.3 Uplink Payload ==

378

379

=== 2.3.2 Sensor Configuration, FPORT~=4 ===

380

381

382

DS03A-NB will only send this command after getting the downlink command **(0x26 02)** from the server.

383

384

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

385

|(% colspan="8" style="background-color:#d9e2f3; color:#0070c0; width:515px" %)**Sensor Configuration FPORT=4**

386

387

|**Value**|(% style="width:75px" %)TDC (unit:sec)|(% style="width:77px" %)Disalarm|(% style="width:96px" %)(((

388

Keep status1

389

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

390

Keep time1(unit: sec)

391

)))|(% style="width:87px" %)Keep status2|(% style="width:97px" %)(((

392

Keep time2(unit: sec)

393

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

394

Alarm interval(unit: min)

395

)))

396

397

Example parse in TTNv3

398

399

[[image:image-20230630155527-3.png||height="146" width="902"]]

* (((

(% style="color:blue" %)**TDC: (default: 0x001C20)**

404

)))

405

406

Uplink interval for the Open/Close Event, default value is 0x001C20 which is 7200 seconds = 2 hours.

* (((

(% style="color:blue" %)**Disalarm: (default: 0)**

411

)))

412

413

**If Disalarm = 1**, DS03A-NB will only send uplink at every TDC periodically. This is normally use for pulse meter application, in this application, there are many open/close event, and platform only care about the total number of pulse.

414

415

**If Disalarm = 0**, DS03A-NB will send uplink at every TDC periodically and send data on each open/close event. This is useful for the application user need to monitor the open/close event in real-time.

416

417

418

(% style="color:red" %)** Note: When Disalarm=0, a high frequently open/close event will cause lots of uplink and drain battery very fast. **

* (((

(% style="color:blue" %)**Keep Status1 & Keep Time1 & Keep Status2 & Keep Time2**

423

)))

424

425

Shows the configure value of [[Alarm Base on Timeout Feature>>||anchor="H3.3.3A0AlarmBaseonTimeout"]]

* (((

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

431

)))

432

433

When the state of the door sensor has not been changed after the timeout alarm, the device will send a uplink every alarm interval. It will stop the alarm until the state of the door sensor is changed after the timeout alarm.

434

435

436

=== 2.3.3 Real-Time Open/Close Status, Uplink FPORT~=2 ===

437

438

439

DS03A-NB will send this uplink **after** Device Status once join the LoRaWAN network successfully. And DS03A-NB will send uplinks when:

440

441

* Every 2 hours, this interval [[can be changed>>||anchor="H3.3.1A0SetTransmitIntervalTime"]].

442

* There is an Open/Close event. (This info can be disabled by AT+DISALARM=1)

443

444

**1) When (% style="color:blue" %)AT+TTRCHANNEL=1(%%), Uplink Payload totals (% style="color:blue" %)11 bytes. (Default mode)(%%)**

445

446

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

447

|=(% colspan="5" style="background-color:#D9E2F3;color:#0070C0;width:515px" %)**Real-Time Open/Close Status, FPORT=2**

448

449

|(% style="width:95px" %)**Value**|(% style="width:97px" %)(((

450

Status & [[Alarm>>||anchor="H3.3.4A0TTRIG126TTRIG2timeoutstatusalarm"]]

451

)))|(% style="width:95px" %)Total open door events|(% style="width:119px" %)(((

452

The last door open duration (unit: sec)

453

)))|(% style="width:108px" %)[[Unix TimeStamp>>||anchor="H2.5.2UnixTimeStamp"]]

**Status & Alarm:**

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

458

|(% style="background-color:#d9e2f3; color:#0070c0; width:50px" %)**Size(bit)**|(% style="background-color:#d9e2f3; color:#0070c0; width:60px" %)**[bit7:bit4]**|(% style="background-color:#d9e2f3; color:#0070c0; width:80px" %)**bit3**|(% style="background-color:#d9e2f3; color:#0070c0; width:100px" %)**bit2**|(% style="background-color:#d9e2f3; color:#0070c0; width:120px" %)**bit1**|(% style="background-color:#d9e2f3; color:#0070c0; width:105px" %)**bit0**

459

|(% style="width:76px" %)**Value**|(% style="width:96px" %)Reserve|(% style="width:110px" %)(((

460

Count mod

461

)))|(% style="width:106px" %)TDC flag 0:No;1:Yes|(% style="width:148px" %)(((

462

Alarm 0: No Alarm; 1: Alarm

463

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

464

Status 0: Close; 1: Open

465

)))

466

467

[[image:image-20230630155451-2.png||height="246" width="928"]]

* (((

(% style="color:blue" %)**Count mod:Default=0**

472

)))

473

474

0: Uplink total open door times since factory

475

476

1: Uplink total open door times since last FPORT=2 uplink.

477

478

479

* (% style="color:blue" %)**TDC flag**

480

481

When the flag is 1, it means sending packets at normal time intervals.

482

483

Otherwise, it is a packet sent at non-TDC time.

* (((

(% style="color:#0000ff" %)**Alarm**

488

)))

489

490

See [[Alarm Base on Timeout>>||anchor="H3.3.3A0AlarmBaseonTimeout"]]

* (((

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

495

)))

496

497

This bit is 1 when the door sensor is open and 0 when it is close.

* (((

(% style="color:blue" %)**Total open door events**

502

)))

503

504

Total pulse/counting base on open door.

505

506

Range (3 Bytes) : 0x000000 ~~ 0xFFFFFF . Max: 16777215

* (((

(% style="color:blue" %)**The last door open duration**

511

)))

512

513

Door sensor last open duration.

Unit: sec.

[[image:image-20230701094042-1.png||height="154" width="763"]]

518

519

520

**2) When (% style="color:blue" %)AT+TTRCHANNEL=2(%%), Uplink Payload totals (% style="color:blue" %)18 bytes(%%)**(% style="color:blue" %).

521

522

(When the maximum DR of some frequencies is 11 bytes, it will cause the server to receive empty packets)

523

524

(% style="color:red" %)**Note:When using the AT+TTRCHANNEL=2 command, the Datalog function cannot be used.**

525

526

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

527

|=(% colspan="8" style="background-color:#D9E2F3;color:#0070C0; width: 515px;" %)**Real-Time Open/Close Status, FPORT=2**

528

529

|(% style="width:95px" %)**Value**|(% style="width:97px" %)(((

530

Status1 & Alarm1

531

)))|(% style="width:95px" %)Total open door events1|(% style="width:125px" %)(((

532

The last door open duration1 (unit: sec)

533

)))|(% style="width:100px" %)[[Unix TimeStamp>>||anchor="H2.5.2UnixTimeStamp"]]|(% style="width:86px" %)(((

534

Status2 & Alarm2

535

)))|(% style="width:96px" %)Total open door events2|(% style="width:126px" %)The last door open duration2 (unit: sec)

536

537

**Status1 & Alarm1:**

538

539

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

540

|(% style="background-color:#d9e2f3; color:#0070c0; width:50px" %)**Size(bit)**|(% style="background-color:#d9e2f3; color:#0070c0; width:60px" %)**[bit7:bit4]**|(% style="background-color:#d9e2f3; color:#0070c0; width:70px" %)**bit3**|(% style="background-color:#d9e2f3; color:#0070c0; width:100px" %)**bit2**|(% style="background-color:#d9e2f3; color:#0070c0; width:117px" %)**bit1**|(% style="background-color:#d9e2f3; color:#0070c0; width:117px" %)**bit0**

541

|(% style="width:76px" %)**Value**|(% style="width:96px" %)Reserve|(% style="width:99px" %)(((

542

Count mod

543

)))|(% style="width:103px" %)TDC flag 0:No;1:Yes|(% style="width:216px" %)(((

544

Alarm1 0: No Alarm; 1: Alarm (PA8 of pin)

545

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

546

Status1 0: Close; 1: Open (PA8 of pin)

547

)))

548

549

**Status2 & Alarm2:**

550

551

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

552

|(% style="background-color:#d9e2f3; color:#0070c0; width:50px" %)**Size(bit)**|(% style="background-color:#d9e2f3; color:#0070c0; width:60px" %)**[bit7:bit2]**|(% style="background-color:#d9e2f3; color:#0070c0; width:200px" %)**bit1**|(% style="background-color:#d9e2f3; color:#0070c0; width:200px" %)**bit0**

553

|(% style="width:76px" %)**Value**|(% style="width:113px" %)Reserve|(% style="width:219px" %)(((

554

Alarm2 0: No Alarm; 1: Alarm (PA4 of pin)

555

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

556

Status2 0: Close; 1: Open (PA4 of pin)

557

)))

558

559

[[image:image-20230630155908-6.png||height="295" width="927"]]

* (((

(% style="color:blue" %)**Count mod:Default=0**

564

)))

565

566

0: Uplink total open door times since factory

567

568

1: Uplink total open door times since last FPORT=2 uplink.

569

570

571

* (% style="color:blue" %)**TDC flag**

572

573

When the flag is 1, it means sending packets at normal time intervals.

574

575

Otherwise, it is a packet sent at non-TDC time.

* (((

(% style="color:#0000ff" %)**Alarm1 or Alarm2**

580

)))

581

582

See [[Alarm Base on Timeout>>||anchor="H3.3.3A0AlarmBaseonTimeout"]]

* (((

(% style="color:blue" %)**Status1 **(% style="color:#0000ff" %)**or **(% style="color:blue" %)**Status2**

587

)))

588

589

This bit is 1 when the door sensor is open and 0 when it is close.

* (((

(% style="color:blue" %)**Total open door events1 **(% style="color:#0000ff" %)**or**(% style="color:blue" %)** Total open door events2**

594

)))

595

596

Total pulse/counting base on open door.

597

598

Range (3 Bytes) : 0x000000 ~~ 0xFFFFFF . Max: 16777215

* (((

(% style="color:blue" %)**The last door open duration1 **(% style="color:#0000ff" %)**or**(% style="color:blue" %)** The last door open duration2**

603

)))

604

605

Door sensor last open duration.

Unit: sec.

[[image:image-20230701094042-1.png||height="154" width="763"]]

610

611

612

=== 2.3.4 Historical Door Open/Close Event, FPORT~=3 ===

613

614

615

DS03A-NB stores sensor values and users can retrieve these history values via the [[downlink command>>||anchor="H2.5DatalogFeature"]].

616

617

The historical payload includes one or multiplies entries and every entry has the same payload as Real-Time open/close status.

618

619

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

620

|=(% colspan="5" style="background-color:#D9E2F3;color:#0070C0;width:515px" %)**Real-Time Open/Close Status, FPORT=3**

621

622

|(% style="width:95px" %)**Value**|(% style="width:97px" %)(((

623

Status & [[Alarm>>||anchor="H3.3.3A0AlarmBaseonTimeout"]]

624

)))|(% style="width:95px" %)Total open door events|(% style="width:119px" %)(((

625

The last door open duration (unit: sec)

626

)))|(% style="width:108px" %)[[Unix TimeStamp>>||anchor="H2.5.2UnixTimeStamp"]]

**Status & Alarm:**

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

631

|(% style="background-color:#d9e2f3; color:#0070c0; width:50px" %)**Size(bit)**|(% style="background-color:#d9e2f3; color:#0070c0; width:75px" %)**bit7**|(% style="background-color:#d9e2f3; color:#0070c0; width:65px" %)**bit6**|(% style="background-color:#d9e2f3; color:#0070c0; width:50px" %)**[bit5:bit4]**|(% style="background-color:#d9e2f3; color:#0070c0; width:50px" %)**bit3**|(% style="background-color:#d9e2f3; color:#0070c0; width:70px" %)**bit2**|(% style="background-color:#d9e2f3; color:#0070c0; width:80px" %)**bit1**|(% style="background-color:#d9e2f3; color:#0070c0; width:75px" %)**bit0**

632

633

Count mod

634

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

635

TDC flag 0:No; 1:Yes

636

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

637

Alarm 0: No Alarm; 1: Alarm

638

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

639

Status 0:Close; 1: Open

)))

* (((

Each data entry is 11 bytes and has the same structure as [[Real-Time open/close status>>||anchor="H2.3.3A0Real-TimeOpen2FCloseStatus2CUplinkFPORT3D2"]], to save airtime and battery, DS03A-NB will send max bytes according to the current DR and Frequency bands.

644

)))

645

646

For example, in the US915 band, the max payload for different DR is:

647

648

(((

649

**~1. DR0**: max is 11 bytes so one entry of data

)))

(((

**2. DR1**: max is 53 bytes so devices will upload 4 entries of data (total 44 bytes)

)))

(((

**3. DR2**: total payload includes 11 entries of data

)))

(((

**4. DR3**: total payload includes 22 entries of data.

662

)))

663

664

If DS03A-NB doesn't have any data in the polling time. It will uplink 11 bytes of 0

665

666

[[image:image-20230630155556-4.png||height="146" width="938"]]

**Downlink:**

0x31 64 9E 7D 34 64 9E 7E 9C 05

**Uplink:**

45 00 00 00 00 00 00 64 9E 7D 48 40 00 00 00 00 00 63 64 9E 7D 9C 41 00 00 01 00 00 63 64 9E 7D A4 40 00 00 01 00 00 8D 64 9E 7E 31 43 00 00 02 00 00 8D 64 9E 7E 44 48 00 00 02 00 00 1F 64 9E 7E 59 4B 00 00 03 00 00 1F 64 9E 7E 6B

**Parsed Value:**

[COUNTMOD, TDC_FLAG, ALARM, DOOR_STATUS, OPEN_DOOR_TIMES, LAST_DOOR_OPEN_DURATION, TIME]

681

682

683

[SUM,YES,FALSE,OPEN,0,0,2023-06-30 06:59:20],

684

685

[SUM,NO,FALSE,CLOSE,0,99,2023-06-30 07:00:44],

686

687

[SUM,NO,FALSE,OPEN, 1,99,2023-06-30 07:00:52],

688

689

[SUM,NO,FALSE,CLOSE,1,141,2023-06-30 07:03:13],

690

691

[SUM,NO,TRUE,OPEN, 2,141,2023-06-30 07:03:32],

692

693

[PART,NO,FALSE,CLOSE,2,31,2023-06-30 07:03:53],

694

695

[PART,NO,TRUE,OPEN, 3,31,2023-06-30 07:04:11],

696

697

[[image:image-20230630172740-1.png||height="199" width="868"]]

== 2.4 Test Uplink and Change Update Interval ==

702

703

704

By default, Sensor will send uplinks (% style="color:blue" %)**every 2 hours**(%%) & AT+NOUD=8

705

706

User can use below commands to change the (% style="color:blue" %)**uplink interval**.

707

708

(% style="color:#037691" %)**AT+TDC=600 ** (%%) ~/~/ Set Update Interval to 600s

709

710

User can also push the button for more than 1 seconds to activate an uplink.

711

712

713

== 2.5 Multi-Samplings and One uplink ==

714

715

716

To save battery life, DS03A-NB will sample Water Flow data every 15 minutes and send one uplink every 2 hours. So each uplink it will include 8 stored data + 1 real-time data. They are defined by:

717

718

* (% style="color:#037691" %)**AT+TR=900** (%%) ~/~/ The unit is seconds, and the default is to record data once every 900 seconds (15 minutes, the minimum can be set to 180 seconds)

719

720

* (% style="color:#037691" %)**AT+NOUD=8** (%%)~/~/ The device uploads 8 sets of recorded data by default. Up to 32 sets of record data can be uploaded.

721

722

The diagram below explains the relationship between TR, NOUD, and TDC more clearly:

723

724

[[image:1692424376354-959.png]]

725

726

727

== 2.6 Trggier an uplink by external interrupt ==

728

729

730

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

731

732

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

733

734

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

735

736

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

737

738

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

739

740

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

741

742

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

743

744

== 2.7 Alarm for continuously water flow ==

(((

This feature is to monitor and send Alarm for continuously water flow.

)))

(((

Example case is for Toilet water monitoring, if some one push toilet button, the toilet will have water flow. If the toilet button has broken and can't returned to original state, the water flow will keep for hours or days which cause huge waste for water.

)))

(((

To monitor this faulty and send alarm, there are two settings:

)))

* (((

(% style="color:blue" %)**Stop Duration: Unit: Second**

)))

(((

Default: 15s, If DS03A-NB didn't see any water flow in 15s, DS03A-NB will consider stop of water flow event.

)))

* (((

(% style="color:blue" %)**Alarm Timer: Units: Minute; Default 0 minutes (means Alarm disable)**

)))

(((

**Example:** 3 minutes, if DS03A-NB detect a start of water flow event and didn't detect a stop event within Alarm timer, DS03A-NB will send an Alarm to indicate a water flow abnormal alarm.

)))

(((

So for example, If we set stop duration=15s and Alarm Timer=3minutes. If the toilet water flow continuously for more than 3 minutes, Sensor will send an alarm (in Confirmed MODE) to platform.

)))

(((

(% style="color:red" %)**Note:** **After this alarm is send, sensor will consider a stop of water flow and count for another new event. So if water flow waste last for 1 hour, Sensor will keep sending alarm every 3 minutes.**

)))

(((

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

)))

* (((

AT+PTRIG=15,3 ~-~-> Set Stop duration: 15s, Alarm Timer: 3 minutes.

)))

* (((

AT+ PTRIG=15,0 ~-~-> Default Value, disable water waste Alarm.

)))

(((

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

)))

(((

Command: **0xAA aa bb cc**

)))

(((

AA: Command Type Code

)))

(((

aa: Stop duration

)))

(((

bb cc: Alarm Timer

)))

(((

If user send 0xAA 0F 00 03: equal to AT+PTRIG=15,3

)))

== 2.8 Set the calculate flag ==

821

822

823

Feature: Set the calculate flag

824

825

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

826

827

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

828

|=(% style="width: 158px;background-color:#4F81BD;color:white" %)**Command Example**|=(% style="width: 193px;background-color:#4F81BD;color:white" %)**Function**|=(% style="width: 110px;background-color:#4F81BD;color:white" %)**Response**

829

|(% style="width:158px" %)AT+CALCFLAG =1|(% style="width:192px" %)Set the calculate flag to 1.|(% style="width:109px" %)OK

830

|(% style="width:158px" %)AT+CALCFLAG =2|(% style="width:192px" %)Set the calculate flag to 2.|(% style="width:109px" %)OK

831

832

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

833

834

* **Example**: 0XA501 ~/~/ Same as AT+CALCFLAG =1

835

836

== 2.9 Set count number ==

837

838

839

Feature: Manually set the count number

840

841

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

842

843

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

844

|=(% style="width: 160px;background-color:#4F81BD;color:white" %)**Command Example**|=(% style="width: 223px;background-color:#4F81BD;color:white" %)**Function**|=(% style="width: 96px;background-color:#4F81BD;color:white" %)**Response**

845

|(% style="width:160px" %)AT+ SETCNT =0|(% style="width:221px" %)Set the count number to 0.|(% style="width:95px" %)OK

846

|(% style="width:160px" %)AT+ SETCNT =100|(% style="width:221px" %)Set the count number to 100.|(% style="width:95px" %)OK

847

848

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

849

850

* **Example**: 0xA6000001 ~/~/ Same as AT+ SETCNT =1

851

852

* **Example**: 0xA6000064 ~/~/ Same as AT+ SETCNT =100

853

854

== 2.10 Set Transmit Interval Time ==

(((

Feature: Change NB-IoT End Node Transmit Interval.

)))

(((

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

863

)))

864

865

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

866

|=(% style="width: 156px;background-color:#4F81BD;color:white" %)**Command Example**|=(% style="width: 137px;background-color:#4F81BD;color:white" %)**Function**|=(% style="background-color:#4F81BD;color:white" %)**Response**

867

|(% style="width:156px" %)AT+TDC=?|(% style="width:137px" %)Show current transmit Interval|(((

868

30000

869

OK

870

the interval is 30000ms = 30s

871

)))

872

|(% style="width:156px" %)AT+TDC=60000|(% style="width:137px" %)Set Transmit Interval|(((

873

OK

874

Set transmit interval to 60000ms = 60 seconds

)))

(((

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

)))

(((

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

)))

(((

If the downlink payload=0100003C, it means set the END Node's Transmit Interval to 0x00003C=60(S), while type code is 01.

)))

* (((

Example 1: Downlink Payload: 0100001E ~/~/ Set Transmit Interval (TDC) = 30 seconds

891

)))

892

* (((

893

Example 2: Downlink Payload: 0100003C ~/~/ Set Transmit Interval (TDC) = 60 seconds

)))

= 3. Configure DS03A-NB =

900

901

== 3.1 Configure Methods ==

902

903

904

DS03A-NB supports below configure method:

905

906

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

907

908

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

909

910

== 3.2 AT Commands Set ==

911

912

913

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

AT+<CMD> : Run <CMD>

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

918

919

AT+<CMD>=? : Get the value

920

921

922

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

AT : Attention

AT? : Short Help

ATZ : MCU Reset

AT+TDC : Application Data Transmission Interval

931

932

AT+CFG : Print all configurations

933

934

AT+CFGMOD : Working mode selection

935

936

AT+DEUI : Get or set the Device ID

937

938

AT+INTMOD : Set the trigger interrupt mode

939

940

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

941

942

AT+PRO : Choose agreement

943

944

AT+RXDL : Extend the sending and receiving time

945

946

AT+DNSCFG : Get or Set DNS Server

947

948

AT+GETSENSORVALUE : Returns the current sensor measurement

949

950

AT+NOUD : Get or Set the number of data to be uploaded

951

952

AT+CDP : Read or Clear cached data

953

954

AT+SHTEMP: Get or Set alarm of temp

955

956

AT+SHHUM: Get or Set alarm of moisture

957

958

AT+SERVADDR : Server Address

959

960

961

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

962

963

AT+CFM : Upload confirmation mode (only valid for UDP)

964

965

966

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

967

968

AT+CLIENT : Get or Set MQTT client

969

970

AT+UNAME : Get or Set MQTT Username

971

972

AT+PWD : Get or Set MQTT password

973

974

AT+PUBTOPIC : Get or Set MQTT publish topic

975

976

AT+SUBTOPIC : Get or Set MQTT subscription topic

977

978

979

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

980

981

AT+FDR : Factory Data Reset

982

983

AT+PWORD : Serial Access Password

984

985

AT+LDATA : Get the last upload data

986

987

AT+CDP : Read or Clear cached data

988

989

990

= 4. Battery & Power Consumption =

991

992

993

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

994

995

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

996

997

998

= 5. Firmware update =

999

1000

1001

User can change device firmware to::

1002

1003

* Update with new features.

* Fix bugs.

Firmware and changelog can be downloaded from : **[[Firmware download link>>https://www.dropbox.com/sh/l0bszumyrmil3yv/AAAg8LYGeAgDsD_ycCnweD72a?dl=0]]**

1008

1009

Methods to Update Firmware:

1010

1011

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

1012

1013

* Update through UART TTL interface : **[[Instruction>>url:http://wiki.dragino.com/xwiki/bin/view/Main/UART%20Access%20for%20LoRa%20ST%20v4%20base%20model/#H1.LoRaSTv4baseHardware]]**.

= 6. FAQ =

== 6.1 How can I access t BC660K-GL AT Commands? ==

1018

1019

1020

User can access to BC660K-GL directly and send AT Commands.

1021

1022

[[See BC660K-GL AT Command set>>url:https://www.dropbox.com/sh/5f6ssda5fum8rvs/AABT68l8ZzWOvZ5eg2qwOoFda?dl=0]]

= 7. Order Info =

Part Number: (% style="color:blue" %)**DS03A-NB-XX**

1029

1030

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

1031

1032

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

1033

1034

* (% style="color:#037691" %)**1D**(%%): with 1NCE* 10 years 500MB SIM card and Pre-configure to DataCake server

1035

1036

(% style="color:#037691" %)**1NCE SIM Card NB-IoT network coverage**(%%): Austria, Belgium, Bulgaria, Croatia, Czech Republic, Denmark, Finland, Germany, Great Britain, Greece, Hungary, Ireland, Italy, Latvia, Malta, Netherlands, Norway, Puerto Rico, Russia, Slovak , Republic, Slovenia, Spain, Sweden, Switzerland, Taiwan, USA, US Virgin Islands

= 8. Packing Info =

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

1044

1045

* DS03A-NB NB-IoT Door sensor x 1

1046

1047

* External antenna x 1

1048

1049

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

1050

1051

* Device Size: 13.0 x 5 x 4.5 cm

1052

1053

* Device Weight: 150g

1054

1055

* Package Size / pcs : 14.0 x 8x 5 cm

1056

1057

* Weight / pcs : 180g

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

1063

1064

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

1065

1066

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

Wiki source code of DS03A-NB -- NB-IoT Door Sensor User Manual

Applications

Navigation