SW3L-CB -- NB-IoT/LTE-M Flow Sensor User Manual

(% aria-label="image-20231010090810-1.png image widget" contenteditable="false" role="region" tabindex="-1" %)

4

(((

5

(% data-widget="image" style="text-align:center" %)

6

[[image:image-20231010090810-1.png||height="379" width="614"]](% title="Click and drag to resize" %)

7

8

(% style="background-image:url(http://wiki.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220,220,220,0.5); display:none" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||height="15" role="presentation" title="Click and drag to move" width="15"]]

)))

**Table of Contents:**

19

20

(% aria-label="macro:toc widget" contenteditable="false" role="region" tabindex="-1" %)

(((

(% style="background-image:url(http://wiki.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220,220,220,0.5); display:none" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||height="15" role="presentation" title="Click and drag to move" width="15"]]

)))

= 1. Introduction =

== 1.1 What is SW3L-CB NB-IoT/LTE-M Flow Sensor ==

35

36

37

The Dragino SW3L-CB is a (% style="color:blue" %)**NB-IoT/LTE-M Flow Sensor**(%%). It detects water flow volume and uplink to IoT server via NB-IoT network. User can use this to (% style="color:blue" %)**monitor the water usage for buildings**.

38

39

The SW3L-CB will send water flow volume every 20 minutes. It can also detect the (% style="color:blue" %)**water flow status and send Alarm**(%%), to avoid the waste for water usage such as broken toilet case.

40

41

SW3L-CB is designed for both indoor and outdoor use. It has a weatherproof enclosure and industrial level battery to (% style="color:blue" %)**work in low to high temperatures**.

42

43

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

44

45

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

46

47

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

48

49

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

50

51

(% style="background-image:url(http://wiki.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220,220,220,0.5); display:none" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||draggable="true" height="15" role="presentation" title="Click and drag to move" width="15"]](% title="Click and drag to resize" %)

== 1.2 Features ==

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

57

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

58

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

59

* Ultra-low power consumption

60

* Upload water flow volume

61

* Monitor water waste

62

* Multiply Sampling and one uplink

63

* GNSS for Location Report

64

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

65

* Support Bluetooth v5.1 remote configure and update firmware

66

* Uplink on periodically

67

* Downlink to change configure

68

* 8500mAh Battery for long term use

69

* Nano SIM card slot for NB-IoT SIM

70

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

71

72

== 1.3 Specification ==

73

74

75

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

76

77

* Supply Voltage: 2.6v ~~ 3.6v

78

* Operating Temperature: -40 ~~ 85°C

79

80

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

81

82

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

83

84

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

99

* B28 @H-FDD: 750MHz

100

* B66 @H-FDD: 2000MHz

101

* B70 @H-FDD: 2000MHz

102

* B85 @H-FDD: 700MHz

103

104

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

105

106

* Li/SOCI2 un-chargeable battery

107

* Capacity: 8500mAh

108

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

109

* Max continuously current: 130mA

110

* Max boost current: 2A, 1 second

111

112

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

113

114

* STOP Mode: 10uA @ 3.3v

115

* Max transmit power: 350mA@3.3v

116

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

117

118

== 1.4 Flow Sensor Spec ==

(((

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

123

|=(% style="width: 103px; background-color:#4F81BD; color: white;" %)**Model**|=(% style="width: 103px; background-color:#4F81BD; color: white;" %)**SW3L-004**|=(% style="width: 103px; background-color:#4F81BD; color: white;" %)SW3L-006|=(% style="width: 103px; background-color:#4F81BD; color: white;" %)SW3L-010|=(% style="width: 103px; background-color:#4F81BD; color: white;" %)SW3L-020

|(% style="width:152px" %)**Power Consumption**|(% style="width:176px" %)1uA, 3.6v (Sensor Only)|(% style="width:173px" %)1uA, 3.6v (Sensor Only)|(% style="width:165px" %)1uA, 3.6v (Sensor Only)|(% style="width:190px" %)1uA, 3.6v (Sensor Only)

130

131

132

|(% style="width:152px" %)**Humidity Range**|(% style="width:176px" %)35%~~90%RH (no frost)|(% style="width:173px" %)35%~~90%RH (no frost)|(% style="width:165px" %)35%~~90%RH (no frost)|(% style="width:190px" %)35%~~90%RH (no frost)

)))

== 1.5 Applications ==

137

138

139

* Flow Sensor application

140

* Water Control

141

* Toilet Flow Sensor

142

* Monitor Waste water

143

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

144

145

== 1.6 Sleep mode and working mode ==

146

147

148

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

149

150

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

151

152

153

== 1.7 Button & LEDs ==

154

155

156

(% aria-label="1675071855856-879.png image widget" contenteditable="false" role="region" tabindex="-1" %)[[image:Main.User Manual for LoRaWAN End Nodes.D20-LBD22-LBD23-LB_LoRaWAN_Temperature_Sensor_User_Manual.WebHome@1675071855856-879.png||data-widget="image"]](% style="background-image:url(http://wiki.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220,220,220,0.5); display:none" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||draggable="true" height="15" role="presentation" title="Click and drag to move" width="15"]](% title="Click and drag to resize" %)

157

158

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

159

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

160

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

161

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

162

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

163

)))

164

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

165

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

166

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

167

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.

168

)))

169

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

170

171

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

172

173

174

== 1.8 BLE connection ==

175

176

177

SW3L-CB support BLE remote configure and firmware update.

178

179

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:

180

181

* Press button to send an uplink

182

* Press button to active device.

183

* Device Power on or reset.

184

185

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

186

187

188

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

189

190

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

191

192

193

=== 1.9.1 Jumper JP2 ===

194

195

196

Power on Device when put this jumper.

197

198

199

=== 1.9.2 BOOT MODE / SW1 ===

200

201

202

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

203

204

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

205

206

207

=== 1.9.3 Reset Button ===

208

209

210

Press to reboot the device.

211

212

(% style="display:none" %)

213

214

215

=== 1.9.4 SIM Card Direction ===

216

217

218

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

219

220

221

== 1.10 Mechanical ==

222

223

(% style="background-image:url(http://wiki.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220,220,220,0.5); display:none" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||draggable="true" height="15" role="presentation" title="Click and drag to move" width="15"]]

224

225

(% style="background-image:url(http://wiki.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220,220,220,0.5); display:none" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||draggable="true" height="15" role="presentation" title="Click and drag to move" width="15"]](% title="Click and drag to resize" %)[[image:image-20250401133652-1.jpeg]]

226

227

(% style="background-image:url(http://wiki.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220,220,220,0.5); display:none" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||draggable="true" height="15" role="presentation" title="Click and drag to move" width="15"]](% title="Click and drag to resize" %)(% style="display:none" %) (%%)

228

229

**Probe Mechanical:**

230

231

232

(% style="color:blue" %)**004: DW-004 Flow Sensor: diameter: G1/2” / DN15. 450 pulse = 1 L**

233

234

(% style="background-image:url(http://wiki.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220,220,220,0.5); display:none" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||draggable="true" height="15" role="presentation" title="Click and drag to move" width="15"]](% title="Click and drag to resize" %)[[image:image-20250401133716-2.jpeg]]

235

236

237

(% style="color:blue" %)**006: DW-006 Flow Sensor: diameter: G3/4” / DN20. 390 pulse = 1 L**

238

239

(% style="background-image:url(http://wiki.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220,220,220,0.5); display:none" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||draggable="true" height="15" role="presentation" title="Click and drag to move" width="15"]][[image:image-20250401133727-3.jpeg]](% title="Click and drag to resize" %)[[image:image-20250418145635-1.jpeg]]

240

241

242

(% style="color:blue" %)**010: DW-010 Flow Sensor: diameter: G 1” / DN25. 64 pulse = 1 L**

243

244

(% style="background-image:url(http://wiki.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220,220,220,0.5); display:none" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||draggable="true" height="15" role="presentation" title="Click and drag to move" width="15"]][[image:image-20250401133737-4.jpeg]](% title="Click and drag to resize" %)[[image:image-20250418145656-2.jpeg]]

245

246

247

(% style="color:blue" %)**020: DW-020 Flow Sensor: diameter: G 2”/ DN50. 12 pulse = 1 L**

248

249

(% aria-label="image-20231205170947-1.png image widget" contenteditable="false" role="region" tabindex="-1" %)[[image:image-20231205170947-1.png||data-widget="image"]](% style="background-image:url(http://wiki.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220,220,220,0.5); display:none" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||draggable="true" height="15" role="presentation" title="Click and drag to move" width="15"]](% title="Click and drag to resize" %)

250

251

252

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

253

254

== 2.1 Send data to IoT server via NB-IoT/CAT-M1 network ==

255

256

257

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

258

259

Below shows the network structure:

260

261

(% style="background-image:url(http://wiki.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220,220,220,0.5); display:none" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||draggable="true" height="15" role="presentation" title="Click and drag to move" width="15"]][[image:image-20240801165103-2.png]](% title="Click and drag to resize" %)[[image:image-20240803091454-1.png]]

262

263

264

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

265

266

267

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

268

269

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

270

271

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

272

273

Below shows result of different server as a glance.

274

275

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

276

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

277

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

278

(% aria-label="image-20230819113244-8.png image widget" contenteditable="false" role="region" tabindex="-1" %)

279

(((

280

(% data-widget="image" style="text-align:center" %)

281

[[image:image-20230819113244-8.png||height="183" width="367"]](% title="Click and drag to resize" %)

282

283

(% style="background-image:url(http://wiki.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220,220,220,0.5); display:none" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||height="15" role="presentation" title="Click and drag to move" width="15"]]

284

)))

285

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

286

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

287

(% aria-label="image-20230819113244-9.png image widget" contenteditable="false" role="region" tabindex="-1" %)

288

(((

289

(% data-widget="image" style="text-align:center" %)

290

[[image:image-20230819113244-9.png||height="119" width="367"]](% title="Click and drag to resize" %)

291

292

(% style="background-image:url(http://wiki.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220,220,220,0.5); display:none" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||height="15" role="presentation" title="Click and drag to move" width="15"]]

293

)))

294

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

295

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

296

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

297

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

298

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

299

(% aria-label="image-20230819113244-10.png image widget" contenteditable="false" role="region" tabindex="-1" %)

300

(((

301

(% data-widget="image" style="text-align:center" %)

302

[[image:image-20230819113244-10.png||height="104" width="367"]](% title="Click and drag to resize" %)

303

304

(% style="background-image:url(http://wiki.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220,220,220,0.5); display:none" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||height="15" role="presentation" title="Click and drag to move" width="15"]]

305

)))

306

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

307

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

308

(% aria-label="image-20230819113244-11.png image widget" contenteditable="false" role="region" tabindex="-1" %)

309

(((

310

(% data-widget="image" style="text-align:center" %)

311

[[image:image-20230819113244-11.png||height="141" width="367"]](% title="Click and drag to resize" %)

312

313

(% style="background-image:url(http://wiki.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220,220,220,0.5); display:none" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||height="15" role="presentation" title="Click and drag to move" width="15"]]

314

)))

315

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

316

317

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

318

319

320

== 2.2 Payload Types ==

321

322

323

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

**Includes:**

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

328

329

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

330

331

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

332

333

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

334

335

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

336

337

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

338

339

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

340

341

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

342

343

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

344

345

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

346

347

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

348

349

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

350

351

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

352

353

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

354

355

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

356

357

358

**Since firmware V1.1.0**, (% style="color:#4472c4" %)**IMSI**(%%) has been added to payload.

359

360

The following describes the latest payload.

361

362

(% style="color:red" %)**Note: The default is AT+GPS=0 ~/~/ The GPS function is not enabled. Therefore, the GPS collection time in the following example paylaod does not follow the system time, and the latitude and longitude are 0.**

363

364

365

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

366

367

368

This is the General Json Format. As below:

369

370

(% style="color:#4472c4" %)**{"IMEI":"868508065605159","IMSI":"454312901015184","Model":"SW3L-CB","alarm:":0,"pulse":231,"water_flow":0.51,"battery":3.210,"signal":23,"time":"2025-04-09T03:26:55Z","latitude":0.000000,"longitude":0.000000,"gps_time":"1970-01-01T00:00:00Z","1":[0.00,"1970-01-01T00:00:03Z"],"2":[0.00,"1970-01-01T00:00:24Z"],"3":[0.01,"2025-04-09T01:52:23Z"],"4":[0.05,"2025-04-09T01:37:23Z"],"5":[0.00,"1970-01-01T00:00:03Z"],"6":[0.00,"1970-01-01T00:00:24Z"],"7":[0.01,"1970-01-01T00:00:02Z"],"8":[0.05,"1970-01-01T00:00:01Z"]}**

371

372

[[image:image-20250409191512-3.png]](% title="Click and drag to resize" %)

373

374

375

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

376

377

* Alarm, Pulse, Water_Flow , Battery, Signal, Latitude, Longitude & GPS_Timestamp are the value at uplink time.

378

379

* 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): Water Flow, Sampling time.

380

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

381

382

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

383

384

385

This is the HEX Format. As below:

386

387

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

388

389

[[image:image-20250409191144-1.png]](% title="Click and drag to resize" %)(% style="display:none" %)

390

391

392

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

393

394

(% title="Click and drag to resize" %)[[image:image-20250409191227-2.png]]

395

396

(% style="color:blue" %)**Device ID(f+IMEI): **(%%)f862406079156234 = 862406079156234

397

398

399

(% style="color:blue" %)**SIM Card ID(f+IMSI): **(%%)f460087023300060 = 460087023300060

400

401

402

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

403

404

These bytes include the hardware and software version.

405

406

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

407

408

(% style="color:#037691" %)**Lower byte:**(%%) Specify the software version: 0x65=101, means firmware version 1.0.1

409

410

411

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

Ex1: 0x0cd4 = 3284mV

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

417

418

NB-IoT Network signal Strength.

**Ex1: 0x1a = 26**

**0** -113dBm or less

**1** -111dBm

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

427

428

**31** -51dBm or greater

429

430

**99** Not known or not detectable

431

432

433

(% style="color:blue" %)**PA4: Support digital level input below 3.3V**

434

435

(((

436

00 ~-~-> PA4 is at low level.

)))

(((

01 ~-~-> PA4 is at high level.

441

442

443

(% style="color:blue" %)**PB15: Support digital level input below 3.3V**

444

445

(((

446

00 ~-~-> PB15 is at low level.

)))

(((

01 ~-~-> PB15 is at high level.

(((

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

)))

(((

00~-~->Normal uplink.

459

460

01~-~->Water flow abnormal alarm.

461

462

463

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

464

465

(((

466

MOD=0 ~-~-> Uplink Total Pulse since factory

)))

(((

MOD=1 ~-~-> Uplink total pulse since last uplink.

)))

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

)))

)))

)))

(((

The calculate flag is a user defined field, total pulse divided by this mark is the converted water flow rate.

)))

(((

(% style="color:#037691" %)**Example:in the default payload:**

)))

* (((

calculate flag=450: for SW3L-004 Flow Sensor: 450 pulse = 1 L

490

)))

491

* (((

492

calculate flag=390: for SW3L-006 Flow Sensor: 390 pulse = 1 L

493

)))

494

* (((

495

calculate flag=64: for SW3L-010 Flow Sensor: 64 pulse = 1 L

)))

(((

Default value: 450.

)))

(((

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

506

507

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

508

509

510

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

511

512

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

)))

(((

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

)))

(((

The total pulse generated by the flow of water passing through the water meter.

)))

(((

**Example:** 0x00f63e6d(H) = 16137837(D)

)))

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

532

533

Unit Timestamp Example: 66AC833B(H) = 1722581819(D)

534

535

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

536

537

538

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

539

540

541

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

542

543

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

544

"topic": "CB_PUB",

545

"payload": {

546

"IMEI": "864370064394515",

"Model": "SW3L-CB",

"alarm:": 0,

"pulse": 358,

"water_flow": 0.8,

"battery": 3.574,

"signal": 28,

"latitude": 0.0,

"longitude": 0.0,

"gps_time": "2024-08-02T07:14:24Z",

556

"1": [0.8, "2024-08-02T07:12:42Z"],

557

"2": [0.8, "2024-08-02T06:26:44Z"],

558

"3": [0.8, "2024-08-02T06:11:44Z"],

559

"4": [0.8, "2024-07-31T02:05:27Z"],

560

"5": [0.8, "2024-07-31T01:50:27Z"],

561

"6": [0.8, "2024-07-31T01:35:27Z"],

562

"7": [0.8, "2024-07-31T01:20:27Z"],

563

"8": [0.8, "2024-07-31T01:05:27Z"]

}

}**

[[image:image-20240802152036-3.png||height="640" width="1255"]](% title="Click and drag to resize" %)

568

569

570

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

571

572

573

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

574

575

Total_pulse, Water_sum, Alarm, Battery, Signal, latitude & longitude. This payload type only valid for ThingsSpeak Platform.

As below:

(% style="color:#4472c4" %)**field1=Total_pulse value&field2=Water_sum value&filed3=Alarm value&filed4=Battery value&field5=Singal value&filed6=Latitude value&field7=Longitude value**

580

581

[[image:image-20240802154430-4.png||height="570" width="867"]]

582

583

[[image:image-20240802154522-7.png||height="572" width="867"]](% title="Click and drag to resize" %)

584

585

586

= 3. Configure SW3L-CB =

587

588

== 3.1 Configure Methods ==

589

590

591

SW3L-CB supports below configure method:

592

593

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

594

595

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

596

597

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

598

599

== 3.2 Serial Access Password ==

600

601

602

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

603

604

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.

605

606

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

607

608

609

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

610

611

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

612

613

614

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

615

616

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

617

618

619

== 3.3 AT Commands Set ==

620

621

622

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

AT+<CMD> : Run <CMD>

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

627

628

AT+<CMD>=? : Get the value

629

630

631

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

AT : Attention

AT? : Short Help

AT+MODEL : Get module information

638

639

ATZ : Trig a reset of the MCU

640

641

AT+DEUI : Get or set the Device ID

642

643

AT+SLEEP : Get or set the sleep status

644

645

AT+DEBUG : Set more info output

646

647

AT+CFG : Print all settings

648

649

AT+SERVADDR: Get or Set the Server address

650

651

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

652

653

AT+APN : Get or set the APN

654

655

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

656

657

AT+PTRIG : Get or Set Alarm for continuously water flow

658

659

AT+MOD : Get or Set the work mode of device

660

661

AT+CALCFLAG : Get or Set the calculate flag

662

663

AT+SETCNT : Get or set the count at present

664

665

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

666

667

AT+RXDL : Get or Set the receiving time

668

669

AT+GETSENSORVALUE : Returns the current sensor measurement

670

671

AT+DNSCFG : Get or Set DNS Server

672

673

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

674

675

AT+GDNS : Get or Set the DNS

676

677

AT+TLSMOD : Get or Set the TLS mode

678

679

AT+IPTYPE : Set the IPv4 or IPv6

680

681

AT+QSW : Power on and power off BG95 module

682

683

AT+CLOCKLOG: Enable or Disable Clock Logging

684

685

AT+TIMESTAMP : Get or Set UNIX timestamp in second

686

687

AT+GETLOG : Print serial port logs

688

689

690

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

691

692

AT+CLIENT : Get or Set the MQTT clientID

693

694

AT+UNAME : Get or Set the MQTT Username

695

696

AT+PWD : Get or Set the MQTT password

697

698

AT+PUBTOPIC: Get or set MQTT publishing topic

699

700

AT+SUBTOPIC: Get or set MQTT subscription topic

701

702

AT+MQOS : Set the QoS level of MQTT

703

704

705

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

706

707

AT+URI1: Get or set CoAP option 1

708

709

AT+URI2: Get or set CoAP option 2

710

711

AT+URI3: Get or set CoAP option 3

712

713

AT+URI4: Get or set CoAP option 4

714

715

AT+URI5: Get or set CoAP option 5

716

717

AT+URI6: Get or set CoAP option 6

718

719

AT+URI7: Get or set CoAP option 7

720

721

AT+URI8: Get or set CoAP option 8

722

723

724

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

725

726

AT+GNSST : Extend the time to turn on GNSS

727

728

AT+GPS : Turn off and on GPS

729

730

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

731

732

733

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

734

735

AT+PWORD : Get or set the System password

736

737

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

738

739

AT+FDR : Reset Parameters to Factory Default

740

741

AT+CDP : Read or Clear cached data

742

743

AT+LDATA : Get the last upload data

744

745

746

== 3.4 Test Uplink and Change Update Interval ==

747

748

749

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

750

751

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

752

753

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

754

755

User can also push the button for more than 1 second to activate an uplink.(% title="Click and drag to resize" %)

756

757

758

== 3.5 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 SW3L-CB didn't see any water flow in 15s, SW3L-CB will consider stop of water flow event.

)))

* (((

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

)))

(((

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

)))

(((

So for example, If we set stop duration=15s and Alarm Timer=10minutes. If the toilet water flow continuously for more than 10 minutes, Sensor will send an alarm 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 10 minutes.**

)))

(((

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

)))

* (((

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

)))

* (((

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

811

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

812

813

== 3.6 Set Power Output Duration ==

814

815

816

Control the output duration 5V . Before each sampling, device will

817

818

~1. first enable the power output to external sensor,

819

820

2. keep it on as per duration, read sensor value and construct uplink payload

821

822

3. final, close the power output.

823

824

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

825

826

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

827

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

828

|(% style="width:172px" %)AT+5VT=?|(% style="width:210px" %)Show 5V open time.|(% style="width:130px" %)0

829

OK

830

|(% style="width:172px" %)AT+5VT=0|(% style="width:210px" %)Normally closed 5V power supply.|(% style="width:130px" %)OK

831

default setting

832

|(% style="width:172px" %)AT+5VT=1000|(% style="width:210px" %)Close after a delay of 1000 milliseconds.|(% style="width:130px" %)(((

OK

)))

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

839

840

== 3.7 Set the calculate flag ==

841

842

843

Feature: Set the calculate flag

844

845

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

846

847

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

848

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

849

|(% style="width:172px" %)AT+CALCFLAG =450|(% style="width:210px" %)Set the calculate flag to 450.|(% style="width:130px" %)OK

850

|(% style="width:172px" %)AT+CALCFLAG =390|(% style="width:210px" %)Set the calculate flag to 390.|(% style="width:130px" %)OK

851

|(% style="width:172px" %)AT+CALCFLAG =64|(% style="width:210px" %)Set the calculate flag to 64.|(% style="width:130px" %)OK

852

|(% style="width:172px" %)AT+CALCFLAG =12|(% style="width:210px" %)Set the calculate flag to 12.|(% style="width:130px" %)OK

853

854

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

855

856

== 3.8 Set count number ==

857

858

859

Feature: This setting can clear the pulse count to 0 or set it to a custom value.

860

861

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

862

863

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

864

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

865

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

866

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

867

868

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

869

870

== 3.9 Clock logging ==

871

872

873

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.

874

875

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.

876

877

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

878

879

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

880

881

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

882

883

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

884

885

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

886

887

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

888

889

(% aria-label="image-20240408084118-1.png image widget" contenteditable="false" role="region" tabindex="-1" %)[[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-20240408084118-1.png?rev=1.1||alt="image-20240408084118-1.png" data-widget="image"]](% style="background-image:url(http://wiki.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220,220,220,0.5); display:none" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||draggable="true" height="15" role="presentation" title="Click and drag to move" width="15"]](% title="Click and drag to resize" %)

**Example:**

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

894

895

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

896

897

[[image:image-20240802161029-10.png||height="552" width="1042"]](% title="Click and drag to resize" %)

898

899

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

900

901

902

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

903

904

905

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

906

907

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

908

909

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

910

911

[[image:image-20240802165021-11.png||height="550" width="673"]]

912

913

914

== 3.11 Example Query saved historical records ==

915

916

917

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

918

919

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.

920

921

[[image:image-20240802155043-8.png||height="533" width="677"]](% title="Click and drag to resize" %)

922

923

924

== 3.12 Uplink log query ==

925

926

927

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

928

929

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

930

931

[[image:image-20240802155114-9.png||height="522" width="667"]]

932

933

934

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

935

936

937

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

938

939

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

940

941

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

942

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

943

|(% 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=0,a

)))

(((

)))

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

960

OK

961

)))

962

|(% style="width:143px" %)**1**: Enable downlink debugging, users can see the original downlink reception.|(% style="width:229px" %)(((

OK

)))

**Example:**

* AT+DOWNTE=0,0 ~/~/ Disable downlink debugging.

969

* AT+DOWNTE=0,1 ~/~/ Enable downlink debugging.

970

971

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

972

973

No downlink commands for feature

974

975

976

== 3.14 Domain name resolution settings(Since firmware v1.1.0) ==

977

978

979

Feature: Set static DNS resolution IP address.

980

981

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

982

983

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

984

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

985

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

986

AT+BKDNS=?

987

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

1000

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

1001

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

1002

**0:** Disable static DNS resolution

1003

1004

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

1005

)))

1006

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

1007

Set to **0**.

1008

)))

1009

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

1010

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

1011

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

1012

The format is the same as AT+SERVADDR.

1013

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.

1019

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

1020

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

1021

1022

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

1023

1024

No downlink commands for feature.

1025

1026

1027

= 4. Battery & Power Consumption =

1028

1029

1030

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

1031

1032

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

1033

1034

1035

= 5. Firmware update =

1036

1037

1038

User can change device firmware to::

1039

1040

* Update with new features.

* Fix bugs.

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

1045

1046

Methods to Update Firmware:

1047

1048

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

1049

1050

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

1051

1052

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

= 6. FAQ =

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

1057

1058

1059

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

1060

1061

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

1062

1063

1064

== 6.2 How to configure the device through the MQTT subscription function? ==

1065

1066

1067

Subscription content: {AT COMMAND}

1068

1069

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

1070

1071

Setting AT+5VT=500 through Node-RED requires MQTT to send the content {AT+5VT=500}.

1072

1073

(% aria-label="image-20231025162946-2.png image widget" contenteditable="false" role="region" tabindex="-1" %)[[image:http://8.211.40.43/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/PS-NB-NA_NB-IoT_Analog_Sensor_User_Manual/WebHome/image-20231025162946-2.png?rev=1.1||alt="image-20231025162946-2.png" data-widget="image"]](% style="background-image:url(http://wiki.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220,220,220,0.5); display:none" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||draggable="true" height="15" role="presentation" title="Click and drag to move" width="15"]](% title="Click and drag to resize" %)

1074

1075

The serial port displays:

1076

1077

(% aria-label="image-20231025162958-3.png image widget" contenteditable="false" role="region" tabindex="-1" %)[[image:http://8.211.40.43/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/PS-NB-NA_NB-IoT_Analog_Sensor_User_Manual/WebHome/image-20231025162958-3.png?rev=1.1||alt="image-20231025162958-3.png" data-widget="image"]](% style="background-image:url(http://wiki.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220,220,220,0.5); display:none" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||draggable="true" height="15" role="presentation" title="Click and drag to move" width="15"]](% title="Click and drag to resize" %)

1078

1079

1080

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

1081

1082

1083

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.

1084

1085

1086

== 6.4 Can I connect 3rd party flow sensor other than the default one? ==

1087

1088

1089

If a user wants to connect SW3L-CB to a 3rd party flow sensor such as a [[DN50 flow sensor>>https://valvesdirect.net/product/dn-50-irrigation-solenoid-valve-24vac-2-female-inlet-2-female-outlet-600lpm/]], that is possible. A flow sensor with pulse output is needed.

1090

1091

**Below is the notice for the connection:**

1092

1093

~1. Connect the 3rd party flow meter to the pulse input and GND of SW3L-CB.

1094

1095

2. Make sure the pulse output voltage of 3rd party flow sensor is less than 5v.

1096

1097

3. It is not recommended to use SW3L-CB to power the external flow meter, unless you are sure the external flow sensor is low power ( several uA). Otherwise the battery of SW3L-CB will be running out soon.

**Connection:**

[[image:image-20240918172719-1.jpeg||height="464" width="716"]]

= 7. Order Info =

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

1108

1109

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

1110

1111

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

1112

1113

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

1114

1115

(((

1116

(% style="color:blue" %)**YY**(%%): Flow Sensor Model:

)))

(((

* **004:** DW-004 Flow Sensor: diameter: G1/2”/ DN15. 450 pulse = 1 L

)))

(((

* **006:** DW-006 Flow Sensor: diameter: G3/4”/ DN20. 390 pulse = 1 L

)))

(((

* **010:** DW-010 Flow Sensor: diameter: G1”/ DN25. 64 pulse = 1 L

)))

(((

* **020:** DW-020 Flow Sensor: diameter: G2”/ DN50. 12 pulse = 1 L

1133

)))

1134

1135

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

= 8. Packing Info =

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

1141

1142

* SW3L-NB NB-IoT/LTE-M Flow sensor x 1

1143

1144

* External antenna x 1

1145

1146

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

1147

1148

* Device Size: 13.0 x 5 x 4.5 cm

1149

1150

* Device Weight: 150g

1151

1152

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

1153

1154

* Weight / pcs : 180g

1155

1156

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

1162

1163

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

Wiki source code of SW3L-CB -- NB-IoT/LTE-M Flow Sensor User Manual

Applications

Navigation