wiki_test - DRAGINO

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

* Door Open/Close detect

48

* Door open/close statistics

49

* Datalog Feature

50

* Open Alarm Feature

51

* Multiply Sampling and one uplink

52

* Support Bluetooth v5.1 remote configure and update firmware

53

* Uplink on periodically

54

* Downlink to change configure

55

* 8500mAh Battery for long term use

56

* Nano SIM card slot for NB-IoT SIM

57

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

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

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

104

105

== 1.4 Applications ==

106

107

108

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

109

110

111

== 1.5 Sleep mode and working mode ==

112

113

114

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

115

116

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

117

118

119

== 1.6 Button & LEDs ==

120

121

122

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

123

124

125

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

126

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

127

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

128

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

129

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

130

)))

131

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

132

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

133

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

134

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.

135

)))

136

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

137

138

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

139

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 & SIM Direction ==

157

158

159

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

160

161

162

=== 1.8.1 Jumper JP2 ===

;

Power on Device when put this jumper.

167

168

169

=== 1.8.2 BOOT MODE / SW1 ===

170

171

172

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

173

174

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

175

176

177

=== 1.8.3 Reset Button ===

178

179

180

Press to reboot the device.

181

182

(% style="display:none" %)

183

184

185

=== 1.8.4 SIM Card Direction ===

186

187

188

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

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

194

195

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

196

197

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

202

203

204

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

205

206

207

== 1.10 Magnet Distance ==

208

209

210

* Wood Door: 10mm ~~ 30mm

211

* Iron Door: 30 ~~ 45mm

212

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

213

214

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

215

216

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

217

218

219

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.

220

221

222

Below shows the network structure:

223

224

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

225

226

227

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

228

229

230

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

231

232

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

233

234

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

235

236

Below shows result of different server as a glance.

237

238

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

239

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

240

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

241

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

242

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

243

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

244

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

245

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

246

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

247

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

248

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

249

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

250

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

251

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

252

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

253

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

254

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

255

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

256

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

257

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

258

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

259

260

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

261

262

263

== 2.2 Payload Types ==

264

265

266

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

**Includes:**

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

271

272

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

273

274

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

275

276

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

277

278

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

279

280

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

281

282

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

283

284

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

285

286

287

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

288

289

290

(% style="color:red" %)**This is the General Json Format. Payloads in General Json format for single-channel mode and double-channel mode have different byte lengths.**

291

292

293

**The General Json format payload for the single-channel mode is as follows:**

294

295

(% style="color:#4472c4" %)**{"IMEI":"863663062798914","Model":"DS03A-NB","level status":1,"alarm status":0,"door open num":0,"last open time":0,"level status2":1,"alarm status2":0,"door open num2":0,"last open time2":0,"battery":3.34,"signal":17,"1":[1,0,0,"2024/06/11 03:09:07"],"2":[1,0,0,"2024/06/11 02:51:00"],"3":[1,0,0,"2024/06/11 02:36:00"],"4":[8,100,100,"2024/05/30 10:19:53"],"5":[8,100,100,"2024/05/30 10:19:18"],"6":[8,100,100,"2024/05/30 10:17:53"],"7":[8,100,100,"2024/05/30 10:16:53"],"8":[8,100,100,"2024/05/30 10:16:28"]}**

296

297

[[image:image-20240611150437-1.png||height="733" width="958"]]

298

299

300

**The General Json format payload for the double-channel mode is as follows:**

301

302

(% style="color:#4472c4" %)**{"IMEI":"863663062798914","Model":"DS03A-NB","level status":1,"alarm status":0,"door open num":0,"last open time":0,"level status2":1,"alarm status2":0,"door open num2":0,"last open time2":0,"battery":3.34,"signal":15,"1":[1,0,0,1,0,0,"2024/06/11 05:49:07"],"2":[0,200,300,1,0,0,"2024/06/11 05:34:07"],"3":[0,200,300,1,0,0,"2024/06/11 05:19:07"],"4":[0,200,300,1,0,0,"2024/06/11 05:04:07"],"5":[0,200,300,1,0,0,"2024/06/11 04:49:07"],"6":[0,200,300,1,0,0,"2024/06/11 04:34:07"],"7":[0,200,300,1,0,0,"2024/06/11 04:19:07"],"8":[0,200,300,1,0,0,"2024/06/11 04:04:07"]}**

303

304

[[image:image-20240611150520-2.png||height="733" width="945"]]

305

306

307

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

308

309

* level status, alarm status, door open num, last open time, level status2, alarm status2, door open sum2, last open time2, Battery & Signal are the value at uplink time.

310

311

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

312

313

Single-channel mode: level status, door open num, last open time, Sampling time.

314

315

Double-channel mode: level status, door open num, last open time, level status2, door open sum2, last open time2, Sampling time.

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

320

321

322

(% style="color:red" %)**This is the HEX Format. Payloads in HEX format for single-channel mode and double-channel mode have different byte lengths.**

323

324

325

**The HEX format payload for the single-channel mode is as follows:**

326

327

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

328

329

330

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

331

332

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

333

334

[[image:image-20240611151101-6.png||height="753" width="980"]]

335

336

337

**The HEX format payload for the double-channel mode is as follows:**

338

339

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

340

341

342

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

343

344

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

345

346

[[image:image-20240611151206-8.png||height="741" width="961"]]

347

348

349

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

350

351

These bytes include the hardware and software version.

352

353

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

354

355

(% style="color:#037691" %)**Lower byte:**(%%) Specify the software version: 0x7b=123, means firmware version 1.2.3

356

357

358

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

Ex1: 0x0dda = 3546mV

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

364

365

NB-IoT Network signal Strength.

**Ex1: 0x15 = 21**

**0** -113dBm or less

**1** -111dBm

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

374

375

**31** -51dBm or greater

376

377

**99** Not known or not detectable

378

379

380

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

381

382

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

383

384

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

385

386

387

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

388

389

390

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

391

392

**The type3 format payload for the single-channel mode is as follows:**

393

394

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

395

"topic": "2276492",

396

"payload": {

397

"IMEI": "863663062798914",

"Model": "DS03A-NB",

"level status": 1,

"alarm status": 0,

"door open num": 0,

"last open time": 0,

"level status2": 1,

"alarm status2": 0,

"door open num2": 0,

"last open time2": 0,

407

"battery": 3.33,

408

"signal": 22,

409

"1": [1, 0, 0, "2024/06/11 06:08:46"],

410

"2": [1, 0, 0, "2024/06/11 05:49:07"],

411

"3": [1, 0, 0, "2024/06/11 05:34:07"],

412

"4": [1, 0, 0, "2024/06/11 05:19:07"],

413

"5": [1, 0, 0, "2024/06/11 05:04:07"],

414

"6": [1, 0, 0, "2024/06/11 04:49:07"],

415

"7": [1, 0, 0, "2024/06/11 04:34:07"],

416

"8": [1, 0, 0, "2024/06/11 04:19:07"]

417

}

418

}**(%%)

419

[[image:image-20240611151445-9.png||height="663" width="1398"]]

420

421

**The type3 format payload for the double-channel mode is as follows:**

422

423

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

424

"topic": "2276492",

425

"payload": {

426

"IMEI": "863663062798914",

"Model": "DS03A-NB",

"level status": 1,

"alarm status": 0,

"door open num": 0,

"last open time": 0,

"level status2": 1,

"alarm status2": 0,

"door open num2": 0,

"last open time2": 0,

436

"battery": 3.34,

437

"signal": 20,

438

"1": [1, 0, 0, 1, 0, 0, "2024/06/11 06:08:46"],

439

"2": [1, 0, 0, 1, 0, 0, "2024/06/11 05:49:07"],

440

"3": [0, 200, 300, 1, 0, 0, "2024/06/11 05:34:07"],

441

"4": [0, 200, 300, 1, 0, 0, "2024/06/11 05:19:07"],

442

"5": [0, 200, 300, 1, 0, 0, "2024/06/11 05:04:07"],

443

"6": [0, 200, 300, 1, 0, 0, "2024/06/11 04:49:07"],

444

"7": [0, 200, 300, 1, 0, 0, "2024/06/11 04:34:07"],

445

"8": [0, 200, 300, 1, 0, 0, "2024/06/11 04:19:07"]

}

}**

[[image:image-20240611151543-10.png||height="672" width="1417"]]

450

451

452

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

453

454

455

This payload meets ThingSpeak platform requirement. It includes eight fields. Form 1~~8 are:

456

457

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

As below:

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

462

463

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

464

465

[[image:image-20231115154821-3.png||height="695" width="1119"]]

466

467

468

== 2.3 Test Uplink and Change Update Interval ==

469

470

471

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

472

473

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

474

475

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

476

477

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

478

479

480

== 2.4 Multi-Samplings and One uplink ==

481

482

483

(% style="color:red" %)**Notice: The AT+NOUD feature is upgraded to Clock Logging, please refer [[Clock Logging Feature>>||anchor="H2.14Clocklogging28Sincefirmwareversionv1.2.129"]].**

484

485

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:

486

487

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

488

489

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

490

491

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

492

493

[[image:1692424376354-959.png]]

494

495

496

== 2.5 Trggier an uplink by external interrupt ==

497

498

499

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

500

501

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

502

503

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

504

505

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

506

507

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

508

509

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

510

511

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

512

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

513

514

== 2.6 Enable / Disable Alarm ==

515

516

517

Feature: Enable/Disable Alarm for open/close event. Default value 0.

518

519

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

520

521

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

522

|(% style="background-color:#4f81bd; color:white; width:153px" %)**Command Example**|(% style="background-color:#4f81bd; color:white; width:276px" %)**Function**|(% style="background-color:#4f81bd; color:white; width:86px" %)**Response**

523

|(% style="width:154px" %)AT+DISALARM=1|(% style="width:278px" %)End node will only send packets in TDC time.|OK

524

|(% style="width:154px" %)AT+DISALARM=0|(% style="width:278px" %)End node will send packets in TDC time or status change for door sensor|OK

525

526

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

527

528

0xA7 01 ~/~/ Same As AT+DISALARM=1

529

530

0xA7 00 ~/~/ Same As AT+DISALARM=0

531

532

533

== 2.7 Alarm Base on Timeout ==

534

535

536

DS03A-NB can monitor the timeout for a status change, this feature can be used to monitor some events such as door opening too long etc. Related Parameters are:

537

538

* (((

539

(% style="color:blue" %)**Keep Status: Status to be monitor**

540

)))

541

542

(% style="color:#037691" %)**Keep Status = 1**(%%): Monitor Close to Open event

543

544

(% style="color:#037691" %)**Keep Status = 0**(%%): Monitor Open to Close event

* (((

(% style="color:blue" %)**Keep Time: Timeout to send an Alarm**

549

)))

550

551

Range 0 ~~ 65535(0xFFFF) seconds.

552

553

If (% style="color:#037691" %)**keep time = 0**(%%), Disable Alarm Base on Timeout feature.

554

555

If (% style="color:#037691" %)**keep time > 0**(%%), device will monitor the keep status event and send an alarm when status doesn't change after timeout.

* (((

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

560

)))

561

562

(% style="color:#037691" %)**Command: 0xA9 aa bb cc dd**

563

564

**A9:** Command Type Code

565

566

**aa: **01:TTRIG1; 02:TTRIG2

567

568

**bb:** status to be monitored

**cc dd:** timeout.

**1) AT+TTRIG1 : (PA8 of pin)**

574

575

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

576

577

* (((

578

(% style="color:#037691" %)**AT+TTRIG1=1,30** (%%) **~-~->** When the **Keep Status** change from close to open, and device remains in open status for more than 30 seconds. DS03A-NB will send an uplink packet, the Alarm1 bit(the second bit of 1^^st^^ byte of payload) on this uplink packet is set to 1.

579

580

(% style="color:#037691" %)**AT+TTRIG1=0,30** (%%) **~-~->** When the **Keep Status** change from open to close, and device remains in open status for more than 30 seconds. DS03A-NB will send an uplink packet, the Alarm1 bit (the second bit of 1^^st^^ byte of payload) on this uplink packet is set to 1.

)))

* (((

(% style="color:#037691" %)**AT+TTRIG1=0,0** (%%) **~-~-> ** Default Value, disable timeout Alarm.

)))

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

590

591

If user send 0xA9 01 01 00 1E: equal to AT+TTRIG1=1,30 **or** 0xA9 01 00 00 00: Equal to AT+TTRIG1=0,0.

592

593

594

**2) AT+TTRIG2 : (PA4 of pin,need to use AT+TTRCHANNEL=2)**

595

596

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

597

598

* (((

599

(% style="color:#037691" %)**AT+TTRIG2=1,30** (%%) **~-~->** When the **Keep Status** change from close to open, and device remains in open status for more than 30 seconds. DS03A-NB will send an uplink packet, the Alarm2 bit (the second bit of 12^^st^^ byte of payload) on this uplink packet is set to 1.

600

601

(% style="color:#037691" %)**AT+TTRIG2=0,30** (%%) **~-~->** When the **Keep Status** change from open to close, and device remains in open status for more than 30 seconds. DS03A-NB will send an uplink packet, the Alarm2 bit (the second bit of 12^^st^^ byte of payload) on this uplink packet is set to 1.

)))

* (((

(% style="color:#037691" %)**AT+TTRIG2=0,0** (%%) **~-~-> ** Default Value, disable timeout Alarm.

)))

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

611

612

If user send 0xA9 02 00 00 1E: equal to AT+TTRIG2=0,30 **or** 0xA9 02 00 00 00: Equal to AT+TTRIG2=0,0.

613

614

615

== 2.88 TTRIG1 & TTRIG2 timeout status alarm ==

616

617

618

It needs to be used with AT+TTRIG1 or AT+TTRIG2. When TTRIG1 or TTRIG2 times out and causes an alarm, and the status does not change subsequently, an alarm packet will be sent at the alarm interval.

619

620

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

621

622

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

623

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

624

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

625

AT+TTRALARM=0

626

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

627

disable continuous alarm

628

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

629

OK

630

)))

631

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

632

AT+TTRALARM=60

633

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

634

The alarm interval is 60 minutes (unit: minutes)

635

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

OK

)))

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

640

641

Example: 0C aa => AT+TTRALARM= aa

== 2.9 Count Mod ==

Feature: Manually set the count mode.

648

649

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

650

651

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

652

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

653

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

654

AT+COUNTMOD=0

655

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

656

the count value keeps accumulating mode

657

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

658

OK

659

)))

660

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

661

AT+COUNTMOD=1

662

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

663

the count value will be reset after each TDC time(Last Close Duration Reset after each uplink)

664

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

OK

)))

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

669

670

Example: 0B aa => AT+COUNTMOD = second byte

671

672

673

== 2.10 Number of channel of door sensors ==

674

675

676

Feature: Set the number of door sensor channels.

677

678

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

679

680

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

681

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

682

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

683

AT+TTRCHANNEL=1

684

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

685

Set as single channel, only use PA8 pin as interrupt pin.

686

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

687

OK

688

)))

689

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

690

AT+TTRCHANNEL=2

691

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

692

Set as dual channel, use PA8 pin and PA4 pin as interrupt pin.

693

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

OK

)))

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

698

699

Example: 0D aa => AT+TTRCHANNEL = second byte

700

701

702

== 2.11 Clear the open door times and the duration of the last open door ==

703

704

705

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

706

707

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

708

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

709

|(% style="width:155px" %)AT+CLRC|(% style="width:259px" %)clear the open door times and the duration of the last open door.|(% style="width:44px" %)(((

OK

)))

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

714

715

The sensor will clear the open door times and the duration of the last open door.

716

717

718

== 2.12 Set the count value of the number of open door ==

719

720

721

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

722

723

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

724

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

725

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

726

AT+SETCNT=1,100

727

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

728

Set the open door times of PA8 pin to 100 times.

729

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

730

OK

731

)))

732

|(% style="width:155px" %)AT+SETCNT=1,0|(% style="width:259px" %)Clear the open door times of PA8 pin.|(% style="width:44px" %)OK

733

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

734

AT+SETCNT=2,50

735

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

736

Set the open door times of PA4 pin to 100 times.

737

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

OK

)))

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

742

743

0xA6 01 00 00 64 ==> AT+SETCNT=1,100

744

745

0xA6 01 00 00 00 ==> AT+SETCNT=1,0

746

747

0xA6 02 00 00 32 ==> AT+SETCNT=2,50

748

749

750

== 2.13 Clock logging (Since firmware version v1.2.1) ==

751

752

753

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.

754

755

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.

756

757

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

758

759

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

760

761

(% style="color:blue" %)**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.

762

763

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

764

765

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

766

767

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

768

769

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

774

775

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

776

777

(% class="wikigeneratedid" %)

778

[[image:image-20240316150911-1.png||height="493" width="1144"]]

779

780

(% class="wikigeneratedid" %)

781

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

782

783

784

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

785

786

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

787

788

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

789

* **Example 1**: Downlink Payload:** 0A0104B00F08** ~/~/ Set SHT record time: AT+CLOCKLOG=1,1200,15,8

790

791

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

792

793

794

== 2.14 Example Query saved historical records ==

795

796

797

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

798

799

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.

800

801

(% class="wikigeneratedid" %)

802

[[image:image-20240316151014-2.png||height="632" width="825"]]

803

804

805

== 2.15 Uplink log query ==

806

807

808

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

809

810

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

811

812

[[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/PS-NB-NA_NB-IoT_Analog_Sensor_User_Manual/WebHome/image-20240407191922-2.png?width=903&height=631&rev=1.1||alt="image-20240407191922-2.png"]]

813

814

815

== 2.16 Scheduled domain name resolution ==

816

817

818

This command is used to set up scheduled domain name resolution.

819

820

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

821

822

* (% style="color:#037691" %)**AT+DNSTIMER=XX **(%%)~/~/ Unit: hour

823

824

After setting this command, domain name resolution will be performed regularly.

825

826

827

== 2.17 Set the QoS level ==

828

829

830

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

831

832

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

833

834

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

835

836

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

837

838

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

839

840

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

841

842

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

843

844

845

= 3. Configure DS03A-NB =

846

847

== 3.1 Configure Methods ==

848

849

850

DS03A-NB supports below configure method:

851

852

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

853

854

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

855

(% style="display:none" %)

856

857

== 3.2 Serial Access Password ==

858

859

860

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

861

862

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.

863

864

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

865

866

867

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

868

869

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

870

871

872

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

873

874

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

875

876

877

== 3.3 AT Commands Set ==

878

879

880

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

AT+<CMD> : Run <CMD>

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

885

886

AT+<CMD>=? : Get the value

887

888

889

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

AT : Attention

AT? : Short Help

ATZ : MCU Reset

AT+TDC : Application Data Transmission Interval

898

899

AT+CFG : Print all configurations

900

901

AT+CFGMOD : Working mode selection

902

903

AT+DEUI : Get or set the Device ID

904

905

AT+INTMOD : Set the trigger interrupt mode

906

907

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

908

909

AT+PRO : Choose agreement

910

911

AT+RXDL : Extend the sending and receiving time

912

913

AT+DNSCFG : Get or Set DNS Server

914

915

AT+GETSENSORVALUE : Returns the current sensor measurement

916

917

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

918

919

AT+CDP : Read or Clear cached data

920

921

AT+SHTEMP: Get or Set alarm of temp

922

923

AT+SHHUM: Get or Set alarm of moisture

924

925

AT+SERVADDR : Server Address

926

927

928

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

929

930

AT+CLIENT : Get or Set MQTT client

931

932

AT+UNAME : Get or Set MQTT Username

933

934

AT+PWD : Get or Set MQTT password

935

936

AT+PUBTOPIC : Get or Set MQTT publish topic

937

938

AT+SUBTOPIC : Get or Set MQTT subscription topic

939

940

941

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

942

943

AT+FDR : Factory Data Reset

944

945

AT+PWORD : Serial Access Password

946

947

AT+LDATA : Get the last upload data

948

949

AT+CDP : Read or Clear cached data

950

951

952

= 4. Battery & Power Consumption =

953

954

955

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

956

957

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

958

959

960

= 5. Firmware update =

961

962

963

User can change device firmware to::

964

965

* Update with new features.

* Fix bugs.

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

970

971

Methods to Update Firmware:

972

973

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

974

975

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

976

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

= 6. FAQ =

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

981

982

983

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

984

985

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

986

987

988

== 6.2 How to configure the certificate? ==

989

990

991

User can can refer to this [[description>>url:http://wiki.dragino.com/xwiki/bin/view/How%20to%20configure%20the%20certificate%3F/]] to configure the certificate.

= 7. Order Info =

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

998

999

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

1000

1001

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

1002

1003

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

1004

1005

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

1012

1013

* DS03A-NB NB-IoT Door sensor x 1

1014

1015

* External antenna x 1

1016

1017

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

1018

1019

* Device Size: 13.0 x 5 x 4.5 cm

1020

1021

* Device Weight: 150g

1022

1023

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

1024

1025

* Weight / pcs : 180g

1026

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

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

1032

1033

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

1034

1035

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

Wiki source code of wiki_test

Applications

Navigation