General Manual for -CB , -CS models

(% class="wikigeneratedid" id="HTableofContents:" %)

6

**Table of Contents:**

= 1. The use of this guideline =

11

12

This configure instruction is for Dragino NB-IoT models with -NB or -NS suffix, for example DDS75-NB. These models use the same NB-IoT Module **[[BC660K-GL>>https://www.quectel.com/product/lpwa-bc660k-gl-nb2]]** and has the same software structure. The have the same configure instruction to different IoT servers. Use can follow the instruction here to see how to configure to connect to those servers.

13

14

= 2. Attach Network =

15

16

== 2.1 General Configure to attach network ==

17

18

To attache NB-IoT sensors to NB-IoT Network, You need to:

19

20

1. Get a NB-IoT SIM card from Service Provider. (Not the same as the SIM card we use in mobile phone)

21

1. Power Off End Node ( See below for the power off/on position)

22

1. Insert the SIM card to Sensor. ( See below for direction)

23

1. Power On End Node

24

1. [[Configure APN>>http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20configure%20APN%20in%20the%20node/]] in the sensor (AT+APN=<APN>), example AT+APN=iot.1nce.net

25

26

[[image:image-20240208102804-1.png||height="286" width="696"]]

27

28

[[image:image-20230808205045-1.png||height="293" width="438"]]

29

30

After doing above, the NB-IoT Sensors should be able to attach to NB-IoT network .

31

32

The -NB and -NS models support (% style="color:blue" %)**LTE Cat NB2**(%%), with below frequency band: multiple frequency bands of (% style="color:blue" %)**B1/B2/B3/B4/B5/B8/B12/B13/B14/B17/B18/B19/B20/B25/B28/B66/B70/B85**(%%) . Make sure you use a the NB-IoT SIM card.

33

34

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

35

|(% style="background-color:#4f81bd; color:white; width:117px" %)**SIM Provider**|(% style="background-color:#4f81bd; color:white; width:151px" %)**AT+APN=**|(% style="background-color:#4f81bd; color:white; width:474px" %)**NB-IoT Coverage**|(% style="background-color:#4f81bd; color:white; width:135px" %)**Comments**

36

|(% style="width:117px" %)**[[1NCE>>https://1nce.com]]**|(% style="width:151px" %)iot.1nce.net|(% style="width:474px" %)(((

37

**[[Coverage Reference Link>>https://1nce.com/en-ap/1nce-connect]]**

38

39

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, UK, US Virgin Islands

40

)))|(% style="width:135px" %)UK: Band20

41

|(% style="width:117px" %)China Mobile|(% style="width:151px" %)No need configure|(% style="width:474px" %)China Mainland, HongKong|(% style="width:135px" %)

42

|(% style="width:117px" %)China Telecom|(% style="width:151px" %)ctnb|(% style="width:474px" %)China Mainland|(% style="width:135px" %)

43

44

== 2.2 Speed Up Network Attach time ==

45

46

BC660K-GL supports multi bands (% style="color:blue" %)**B1/B2/B3/B4/B5/B8/B12/B13/B14/B17/B18/B19/B20/B25/B28/B66/B70/B85. **(%%) It will search one by one and try to attach, this will take a lot of time and even cause attach fail and show **Signal Strenght:99**. User can lock the band to specify band for its operator to make this faster.

47

48

(% style="color:#037691" %)**AT+QBAND? **(%%) ~/~/ Check what is the current used frequency band

49

(% style="color:#037691" %)**AT+QBAND=1,4 **(%%) ~/~/ Set to use 1 frequency band. Band4

50

(% style="color:#037691" %)**Europe General**(%%) **AT+QBAND=2,8,20 ** ~/~/ Set to use 2 frequency bands. Band 8 and Band 20

51

(% style="color:#037691" %)**Global General**(%%) : **AT+QBAND=10,8,20,28,2,4,12,13,66,85,5**

52

53

(% style="color:#037691" %)**Verizon**(%%)** ** AT+QBAND=1,13

54

(% style="color:#037691" %)**AT&T**(%%) AT+QBAND=3,12,4,2

55

(% style="color:#037691" %)**Telstra**(%%) AT+QBAND=1,28

56

(% style="color:#037691" %)**Softband**(%%) AT+QBAND=2,3,8

57

58

After connection is successful, user can use (% style="color:#037691" %)**AT+QENG=0 **(%%) to check which band is actually in used.

59

60

See bands used for different provider:** [[NB-IoT Deployment , Bands, Operator list>>http://wiki.dragino.com/xwiki/bin/view/Main/NB-IoT%20Deployment%20%2C%20Bands%2C%20Operator%20list/]]**

61

62

= 3. Configure to connect to different servers =

63

64

== 3.1 General UDP Connection ==

65

66

The NB-IoT Sensor can send packet to server use UDP protocol.

67

68

=== 3.1.1 Simulate UDP Connection by PC tool ===

69

70

We can use PC tool to simulate UDP connection to make sure server works ok.

71

72

[[image:image-20230802112413-1.png||height="468" width="1024"]]

73

74

=== 3.1.2 Configure NB-IoT Sensor ===

75

76

==== 3.1.2.1 AT Commands ====

77

78

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

79

80

* (% style="color:#037691" %)**AT+PRO=2,0** (%%) ~/~/ Set to use UDP protocol to uplink ,Payload Type select Hex payload

81

82

* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5601** (%%) ~/~/ Set UDP server address and port

83

84

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

85

86

==== 3.1.2.2 Uplink Example ====

87

88

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

89

90

== 3.2 General MQTT Connection ==

91

92

The NB-IoT Sensor can send packet to server use MQTT protocol.

93

94

Below are the commands.

95

96

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

97

98

* (% style="color:#037691" %)**AT+PRO=3,0** (%%) ~/~/ Set to use MQTT protocol to uplink, Payload Type select Hex payload.

99

100

* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,1883** (%%) ~/~/ Set MQTT server address and port

101

102

* (% style="color:#037691" %)**AT+CLIENT=CLIENT** (%%) ~/~/ Set up the CLIENT of MQTT

103

104

* (% style="color:#037691" %)**AT+UNAME=UNAME** (%%) ~/~/ Set the username of MQTT

105

106

* (% style="color:#037691" %)**AT+PWD=PWD** (%%) ~/~/ Set the password of MQTT

107

108

* (% style="color:#037691" %)**AT+PUBTOPIC=NSE01_PUB** (%%) ~/~/ Set the sending topic of MQTT

109

110

* (% style="color:#037691" %)**AT+SUBTOPIC=NSE01_SUB** (%%) ~/~/ Set the subscription topic of MQTT

111

112

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

113

114

[[image:image-20230802112413-5.png||height="530" width="987"]]

115

116

(% style="color:red" %)**Notice: MQTT protocol has a much higher power consumption compare with UDP/CoAP protocol. Please check the power analyze document and adjust the uplink period to a suitable interval.**

117

118

== 3.3 [[ThingSpeak>>url:https://thingspeak.com/]] (via MQTT) ==

119

120

=== 3.3.1 Get MQTT Credentials ===

121

122

[[ThingSpeak>>url:https://thingspeak.com/]] connection uses MQTT Connection. So we need to get MQTT Credentials first. You need to point MQTT Devices to ThingSpeak Channel as well.

123

124

[[image:image-20230802112413-6.png||height="336" width="925"]]

125

126

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

127

128

=== 3.3.2 Simulate with MQTT.fx ===

129

130

==== 3.3.2.1 Establish MQTT Connection ====

131

132

After we got MQTT Credentials, we can first simulate with PC tool MQTT.fx tool to see if the Credentials and settings are fine.

133

134

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

135

136

* (% style="color:#037691" %)**Broker Address:**(%%) mqtt3.thingspeak.com

137

138

* (% style="color:#037691" %)**Broker Port:**(%%) 1883

139

140

* (% style="color:#037691" %)**Client ID:**(%%) <Your ThingSpeak MQTT ClientID>

141

142

* (% style="color:#037691" %)**User Name:**(%%) <Your ThingSpeak MQTT User Name>

143

144

* (% style="color:#037691" %)**Password:**(%%) <Your ThingSpeak MQTT Password>

145

146

==== 3.3.2.2 Publish Data to ThingSpeak Channel ====

147

148

[[image:image-20230802112413-9.png]]

149

150

[[image:image-20230802112413-10.png]]

151

152

(% style="color:blue" %)**In MQTT.fx, we can publish below info:**

153

154

* (% style="color:#037691" %)**Topic:**(%%) channels/YOUR_CHANNEL_ID/publish

155

156

* (% style="color:#037691" %)**Payload:**(%%) field1=63&field2=67&status=MQTTPUBLISH

157

158

Where 63 and 67 are the value to be published to field1 & field2.

159

160

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

161

162

[[image:image-20230802112413-11.png||height="539" width="901"]]

163

164

=== 3.3.3 Configure NB-IoT Sensor for connection ===

165

166

==== 3.3.3.1 AT Commands: ====

167

168

In the NB-IoT, we can run below commands so to publish the channels like MQTT.fx

169

170

* (% style="color:blue" %)**AT+PRO=3,1** (%%) ~/~/ Set to use ThingSpeak Server and Related Payload

171

172

* (% style="color:blue" %)**AT+CLIENT=<Your ThingSpeak MQTT ClientID>**

173

174

* (% style="color:blue" %)**AT+UNAME=<Your ThingSpeak MQTT User Name>**

175

176

* (% style="color:blue" %)**AT+PWD=<Your ThingSpeak MQTT Password>**

177

178

* (% style="color:blue" %)**AT+PUBTOPIC=<YOUR_CHANNEL_ID>**

179

180

* (% style="color:blue" %)**AT+SUBTOPIC=<YOUR_CHANNEL_ID>**

181

182

==== 3.3.3.2 Uplink Examples ====

183

184

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

For SE01-NB

For DDS20-NB

For DDS45-NB

For DDS75-NB

For NMDS120-NB

For SPH01-NB

For NLM01-NB

For NMDS200-NB

For CPN01-NB

For DS03A-NB

For SN50V3-NB

==== 3.3.3.3 Map fields to sensor value ====

209

210

When NB-IoT sensor upload to ThingSpeak. The payload already specify which fileds related to which sensor value. Use need to create fileds in Channels Settings. with name so to see the value correctly.

211

212

[[image:image-20230802112413-12.png||height="504" width="1011"]]

213

214

[[image:image-20230802112413-13.png||height="331" width="978"]]

215

216

Below is the NB-IoT Product Table show the mapping.

217

218

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

219

|(% style="background-color:#4f81bd; width:143px" %) |(% style="background-color:#4f81bd; color:white; width:103px" %)Field1|(% style="background-color:#4f81bd; color:white; width:102px" %)Field2|(% style="background-color:#4f81bd; color:white; width:157px" %)Field3|(% style="background-color:#4f81bd; color:white; width:154px" %)Field4|(% style="background-color:#4f81bd; color:white; width:153px" %)Field5|(% style="background-color:#4f81bd; color:white; width:151px" %)Field6|(% style="background-color:#4f81bd; color:white; width:160px" %)Field7|(% style="background-color:#4f81bd; color:white; width:152px" %)Field8|(% style="background-color:#4f81bd; color:white; width:67px" %)Field9|(% style="background-color:#4f81bd; color:white; width:69px" %)Field10

|(% colspan="1" rowspan="1" style="background-color:#4f81bd; color:white; width:143px" %)DS03A-NB|(% colspan="1" rowspan="1" style="width:103px" %)level|(% colspan="1" rowspan="1" style="width:102px" %)alarm|(% colspan="1" rowspan="1" style="width:157px" %)pb14door open num|(% colspan="1" rowspan="1" style="width:154px" %)pb14 last open time|(% colspan="1" rowspan="1" style="width:153px" %)pb15 level status|(% colspan="1" rowspan="1" style="width:151px" %)pb15 alarm status|(% colspan="1" rowspan="1" style="width:160px" %)pb15 door open num|(% colspan="1" rowspan="1" style="width:152px" %)pb15 last open time|(% colspan="1" rowspan="1" style="width:67px" %)Battery|(% colspan="1" rowspan="1" style="width:69px" %)RSSI

231

|(% colspan="1" rowspan="1" style="background-color:#4f81bd; color:white; width:143px" %)SN50V3-NB mod1|(% colspan="1" rowspan="1" style="width:103px" %)mod|(% colspan="1" rowspan="1" style="width:102px" %)Battery|(% colspan="1" rowspan="1" style="width:157px" %)RSSI|(% colspan="1" rowspan="1" style="width:154px" %)DS18B20 Temp|(% colspan="1" rowspan="1" style="width:153px" %)exit_state/input PA4|(% colspan="1" rowspan="1" style="width:151px" %)adc0|(% colspan="1" rowspan="1" style="width:160px" %)Temperature |(% colspan="1" rowspan="1" style="width:152px" %)Humidity|(% colspan="1" rowspan="1" style="width:67px" %) |(% colspan="1" rowspan="1" style="width:69px" %)

232

|(% colspan="1" style="background-color:#4f81bd; color:white; width:143px" %)SN50V3-NB mod2|(% colspan="1" style="width:103px" %)mod|(% colspan="1" style="width:102px" %)Battery|(% colspan="1" style="width:157px" %)RSSI|(% colspan="1" style="width:154px" %)DS18B20 Temp|(% colspan="1" style="width:153px" %)exit_state/input PA4|(% colspan="1" style="width:151px" %)adc0|(% colspan="1" style="width:160px" %)distance|(% colspan="1" style="width:152px" %) |(% colspan="1" style="width:67px" %) |(% colspan="1" style="width:69px" %)

233

|(% colspan="1" style="background-color:#4f81bd; color:white; width:143px" %)SN50V3-NB mod3|(% colspan="1" style="width:103px" %)mod|(% colspan="1" style="width:102px" %)Battery|(% colspan="1" style="width:157px" %)RSSI|(% colspan="1" style="width:154px" %)adc0|(% colspan="1" style="width:153px" %)exit_state/input PA4|(% colspan="1" style="width:151px" %)adc1|(% colspan="1" style="width:160px" %)Temperature|(% colspan="1" style="width:152px" %)Humidity|(% colspan="1" style="width:67px" %)adc4|(% colspan="1" style="width:69px" %)

234

|(% colspan="1" style="background-color:#4f81bd; color:white; width:143px" %)SN50V3-NB mod4|(% colspan="1" style="width:103px" %)mod|(% colspan="1" style="width:102px" %)Battery|(% colspan="1" style="width:157px" %)RSSI|(% colspan="1" style="width:154px" %)DS18B20 Temp|(% colspan="1" style="width:153px" %)adc0|(% colspan="1" style="width:151px" %)exit_state/input PA4|(% colspan="1" style="width:160px" %)DS18B20 Temp2|(% colspan="1" style="width:152px" %)DS18B20 Temp3|(% colspan="1" style="width:67px" %) |(% colspan="1" style="width:69px" %)

235

|(% colspan="1" style="background-color:#4f81bd; color:white; width:143px" %)SN50V3-NB mod5|(% colspan="1" style="width:103px" %)mod|(% colspan="1" style="width:102px" %)Battery|(% colspan="1" style="width:157px" %)RSSI|(% colspan="1" style="width:154px" %)DS18B20 Temp|(% colspan="1" style="width:153px" %)adc0|(% colspan="1" style="width:151px" %)exit_state/input PA4|(% colspan="1" style="width:160px" %)Weight|(% colspan="1" style="width:152px" %) |(% colspan="1" style="width:67px" %) |(% colspan="1" style="width:69px" %)

236

|(% colspan="1" style="background-color:#4f81bd; color:white; width:143px" %)SN50V3-NB mod6|(% colspan="1" style="width:103px" %)mod|(% colspan="1" style="width:102px" %)Battery|(% colspan="1" style="width:157px" %)RSSI|(% colspan="1" style="width:154px" %)count|(% colspan="1" style="width:153px" %) |(% colspan="1" style="width:151px" %) |(% colspan="1" style="width:160px" %) |(% colspan="1" style="width:152px" %) |(% colspan="1" style="width:67px" %) |(% colspan="1" style="width:69px" %)

237

238

== 3.4 [[Datacake>>https://datacake.co/]] ==

239

240

(% class="wikigeneratedid" %)

241

Dragino NB-IoT sensors has its template in **[[Datacake>>https://datacake.co/]]** Platform. There are two version for NB Sensor,

242

243

(% class="wikigeneratedid" %)

244

As example for S31B-NB. there are two versions: **S31B-NB-1D and S31B-NB-GE.**

245

246

* (% style="color:blue" %)**S31B-NB-1D**(%%): This version have pre-configure DataCake connection. User just need to Power on this device, it will auto connect send data to DataCake Server.

247

248

* (% style="color:blue" %)**S31B-NB-GE**(%%): This verson doesn't have pre-configure Datacake connection. User need to enter the AT Commands to connect to Datacake. See below for instruction.

249

250

=== 3.4.1 For device Already has template ===

251

252

==== 3.4.1.1 Create Device ====

253

254

(% style="color:blue" %)**Add Device**(%%) in DataCake.

255

256

[[image:image-20230808162301-1.png||height="453" width="952"]]

257

258

[[image:image-20230808162342-2.png||height="541" width="952"]]

259

260

(% style="color:blue" %)**Choose the correct model**(%%) from template.

261

262

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

263

264

(% style="color:blue" %)**Fill Device ID**(%%). The device ID needs to be filled in with IMEI, and a prefix of(% style="color:blue" %)** 'f' **(%%)needs to be added.

265

266

[[image:image-20230808163612-7.png||height="549" width="952"]]

267

268

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

269

270

[[image:image-20230808163049-6.png||height="544" width="926"]]

271

272

=== 3.4.2 For Device already registered in DataCake before shipped ===

273

274

==== 3.4.2.1 Scan QR Code to get the device info ====

275

276

Users can use their phones or computers to scan QR codes to obtain device data information.

277

278

[[image:image-20230808170051-8.png||height="255" width="259"]]

279

280

[[image:image-20230808170548-9.png]]

281

282

==== 3.4.2.2 Claim Device to User Account ====

283

284

By Default, the device is registered in Dragino's DataCake Account. User can Claim it to his account.

285

286

=== 3.4.3 Manual Add Decoder in DataCake ( don't use the template in DataCake) ===

287

288

**Step1: Add a device**

289

290

[[image:image-20240129170024-1.png||height="330" width="900"]]

291

292

**Step2: Choose your device type,please select dragino NB-IOT device**

293

294

[[image:image-20240129170216-2.png||height="534" width="643"]]

295

296

**Step3: Choose to create a new device**

297

298

[[image:image-20240129170539-3.png||height="459" width="646"]]

299

300

**Step4: Fill in the device ID of your NB device**

301

302

[[image:image-20240202111546-1.png||height="378" width="651"]]

303

304

**Step5: Please select your device plan according to your needs and complete the creation of the device**

305

306

[[image:image-20240129171236-6.png||height="450" width="648"]]

307

308

**Step6: Please add the decoder at the payload decoder of the device configuration.**

309

310

**Decoder location:**[[dragino-end-node-decoder/Datacake-Dragino_NB at main · dragino/dragino-end-node-decoder (github.com)>>url:https://github.com/dragino/dragino-end-node-decoder/tree/main/Datacake-Dragino_NB]]

311

312

[[image:image-20240129172056-7.png||height="457" width="816"]]

313

314

[[image:image-20240129173116-9.png||height="499" width="814"]]

315

316

**Step7: Add the output of the decoder as a field**

317

318

[[image:image-20240129173541-10.png||height="592" width="968"]]

319

320

**Step8: Customize the dashboard and use fields as parameters of the dashboard**

321

322

[[image:image-20240129174518-11.png||height="147" width="1042"]]

323

324

[[image:image-20240129174657-12.png||height="538" width="916"]]

325

326

[[image:image-20240129174840-13.png||height="536" width="750"]]

327

328

=== 3.4.4 For device have not configured to connect to DataCake ===

329

330

(% class="lead" %)

331

Use AT command for connecting to DataCake

332

333

(% style="color:blue" %)**AT+PRO=2,0**

334

335

(% style="color:blue" %)**AT+SERVADDR=67.207.76.90,4445**

336

337

== 3.5 Node-Red (via MQTT) ==

338

339

=== 3.5.1 Configure [[Node-Red>>http://wiki.dragino.com/xwiki/bin/view/Main/Node-RED/]] ===

340

341

Take S31-NB UDP protocol as an example.

342

343

Dragino provides input flow examples for the sensors.

344

345

User can download the required JSON file through Dragino Node-RED input flow template.

346

347

Download sample JSON file link: [[https:~~/~~/www.dropbox.com/sh/mduw85jcuwsua22/AAAvwPhg9z6dLjJhmZjqBf_ma?dl=0>>url:https://www.dropbox.com/sh/mduw85jcuwsua22/AAAvwPhg9z6dLjJhmZjqBf_ma?dl=0]]

348

349

We can directly import the template.

350

351

The templates for S31-NB and NB95S31B are the same.

352

353

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

354

355

Please select the NB95S31B template.

356

357

[[image:image-20230809173310-5.png||height="558" width="926"]]

358

359

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

360

361

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

362

363

Successfully imported template.

364

365

[[image:image-20230809173835-8.png||height="515" width="860"]]

366

367

Users can set UDP port.

368

369

[[image:image-20230809174053-9.png]]

370

371

=== 3.5.2 Simulate Connection ===

372

373

We have completed the configuration of UDP. We can try sending packets to node red.

374

375

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

376

377

[[image:image-20230810084048-2.png||height="535" width="1052"]]

378

379

=== 3.5.3 Configure NB-IoT Sensors ===

380

381

* (% style="color:#037691" %)**AT+PRO=3,0 or 3,5 ** (%%) **~/~/ hex format or json format**

382

* (% style="color:#037691" %)**AT+SUBTOPIC=<device name>or User Defined**

383

* (% style="color:#037691" %)**AT+PUBTOPIC=<device name>or User Defined**

384

* (% style="color:#037691" %)**AT+CLIENT=<device name> or User Defined**

385

* (% style="color:#037691" %)**AT+UNAME=<device name> or User Defined**

386

* (% style="color:#037691" %)**AT+PWD=“Your device token”**

387

388

== 3.6 ThingsBoard.Cloud (via MQTT) ==

389

390

=== 3.6.1 Configure ThingsBoard ===

391

392

==== 3.6.1.1 Create Device ====

393

394

Create a New Device in [[ThingsBoard>>url:https://thingsboard.cloud/]]. Record Device Name which is used for MQTT connection.

395

396

[[image:image-20230802112413-32.png||height="583" width="1066"]]

397

398

==== 3.6.1.2 Create Uplink & Downlink Converter ====

399

400

(% style="color:blue" %)**Uplink Converter**

401

402

The purpose of the decoder function is to parse the incoming data and metadata to a format that ThingsBoard can consume. deviceName and deviceType are required, while attributes and telemetry are optional. Attributes and telemetry are flat key-value objects. Nested objects are not supported.

403

404

To create an uplink converter go to the (% style="color:blue" %)**Integrations center**(%%) -> (% style="color:blue" %)**Data converters**(%%) page and click (% style="color:blue" %)**“plus”** (%%)button. Name it (% style="color:blue" %)**“MQTT Uplink Converter”**(%%) and select type (% style="color:blue" %)"**Uplink"**(%%). Use debug mode for now.

405

406

[[image:image-20230802112413-33.png||height="597" width="1061"]]

407

408

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

409

410

The Downlink converter transforming outgoing RPC message and then the Integration sends it to external MQTT broke

411

412

[[image:image-20230802112413-34.png||height="598" width="1063"]]

413

414

(% style="color:red" %)**Note: Our device payload is already human readable data. Therefore, users do not need to write decoders. Simply create by default.**

415

416

==== 3.6.1.3 MQTT Integration Setup ====

417

418

Go to the (% style="color:blue" %)**Integrations center**(%%) **->** (% style="color:blue" %)**Integrations page**(%%) and click **“(% style="color:blue" %)plus(%%)”** icon to add a new integration. Name it (% style="color:blue" %)**“MQTT Integration”**(%%), select type (% style="color:blue" %)**MQTT**;

419

420

[[image:image-20230802112413-35.png||height="597" width="1062"]]

421

422

* The next steps is to add the recently created uplink and downlink converters;

423

424

[[image:image-20230802112413-36.png||height="598" width="1062"]]

425

426

[[image:image-20230802112413-37.png||height="598" width="1064"]]

427

428

(% style="color:blue" %)**Add a topic filter:**

429

430

Consistent with the theme of the node setting.

431

432

You can also select an MQTT QoS level. We use MQTT QoS level 0 (At most once) by default;

433

434

[[image:image-20230802112413-38.png||height="598" width="1064"]]

435

436

=== 3.6.2 Simulate with MQTT.fx ===

437

438

[[image:image-20230802112413-39.png]]

439

440

[[image:image-20230802112413-40.png||height="525" width="980"]]

441

442

=== 3.6.3 Configure NB-IoT Sensor ===

443

444

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

445

446

* (% style="color:#037691" %)**AT+PRO=3,3 **(%%)** **~/~/ Use MQTT to connect to ThingsBoard. Payload Type set to 3.

447

448

* (% style="color:#037691" %)**AT+SUBTOPIC=<device name>**

449

450

* (% style="color:#037691" %)**AT+PUBTOPIC=<device name>**

451

452

* (% style="color:#037691" %)**AT+CLIENT=<device name> or User Defined**

453

454

* (% style="color:#037691" %)**AT+UNAME=<device name> or User Defined**

455

456

* (% style="color:#037691" %)**AT+PWD=<device name> or User Defined**

457

458

Test Uplink by click the button for 1 second

459

460

[[image:image-20230802112413-41.png||height="496" width="828"]]

461

462

[[image:image-20230802112413-42.png]]

463

464

[[image:image-20230802112413-43.png||height="407" width="825"]]

465

466

== 3.7 [[Tago.io>>url:https://admin.tago.io/]] (via MQTT) ==

467

468

=== 3.7.1 Create device & Get Credentials ===

469

470

We use MQTT Connection to send data to [[Tago.io>>url:https://admin.tago.io/]]. We need to Create Device and Get MQTT Credentials first.

471

472

[[image:image-20230802112413-44.png]]

473

474

[[image:image-20230802112413-45.png]]

475

476

Go to the Device section and create a device. Then, go to the section tokens and copy your device-token.

477

478

[[image:image-20230802112413-46.png]]

479

480

The device needs to enable the TLS mode and set the (% style="color:blue" %)**AT+TLSMOD=1,0**(%%) command.

481

482

(% style="color:blue" %)**On the Connection Profile window, set the following information:**

483

484

* (% style="color:#037691" %)**Profile Name: “Any name”**

485

486

* (% style="color:#037691" %)**Broker Address: mqtt.tago.io**

487

488

* (% style="color:#037691" %)**Broker Port: 8883**

489

490

* (% style="color:#037691" %)**Client ID: “Any value”**

491

492

(% style="color:blue" %)**On the section User credentials, set the following information:**

493

494

* (% style="color:#037691" %)**User Name: “Any value”** (%%) **~/~/ Tago validates your user by the token only**

495

496

* (% style="color:#037691" %)**Password: “Your device token”**

497

498

* (% style="color:#037691" %)**PUBTOPIC: “Any value”**

499

500

* (% style="color:#037691" %)**SUBTOPIC: “Any value”**

501

502

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

503

504

* (% style="color:#037691" %)**AT+PRO=3,0 or 3,5 ** (%%) **~/~/ hex format or json format**

505

506

* (% style="color:#037691" %)**AT+SUBTOPIC=<device name>or User Defined**

507

508

* (% style="color:#037691" %)**AT+PUBTOPIC=<device name>or User Defined**

509

510

* (% style="color:#037691" %)**AT+CLIENT=<device name> or User Defined**

511

512

* (% style="color:#037691" %)**AT+UNAME=<device name> or User Defined**

513

514

* (% style="color:#037691" %)**AT+PWD=“Your device token”**

515

516

=== 3.7.2 Simulate with MQTT.fx ===

517

518

[[image:image-20230802112413-52.png]]

519

520

[[image:image-20230808105300-2.png||height="553" width="1026"]]

521

522

Users can run the (% style="color:blue" %)**AT+PRO=3,5**(%%) command, and the payload will be converted to **JSON format**.

523

524

[[image:image-20230808105217-1.png||height="556" width="1031"]]

525

526

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

527

528

=== 3.7.3 tago data ===

529

530

[[image:image-20230802112413-50.png||height="242" width="1037"]]

531

532

[[image:image-20230802112413-51.png||height="184" width="696"]]

533

534

== 3.8 TCP Connection ==

535

536

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

537

538

* (% style="color:#037691" %)**AT+PRO=4,0 ** (%%) ~/~/ Set to use TCP protocol to uplink(HEX format)

539

540

* (% style="color:#037691" %)**AT+PRO=4,1 ** (%%) ~/~/ Set to use TCP protocol to uplink(JSON format)

541

542

* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5600 ** (%%) ~/~/ to set TCP server address and port

543

544

(% style="color:blue" %)**Sensor Console Output when Uplink:**

545

546

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

547

548

(% style="color:blue" %)**See result in TCP Server:**

549

550

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

551

552

== 3.9 AWS Connection ==

553

554

Users can refer to [[Dragino NB device connection to AWS platform instructions>>http://wiki.dragino.com/xwiki/bin/view/Dragino%20NB%20device%20connection%20to%20AWS%20platform%20instructions/#H1.LogintotheplatformandfindIoTcore]]

555

556

= 4. MQTT/UDP/TCP downlink =

557

558

== 4.1 MQTT (via MQTT.fx) ==

559

560

Configure MQTT connections properly and send downlink commands to configure nodes through the Publish function of MQTT.fx//.//

561

562

**1.** Configure node MQTT connection (via MQTT.fx):

563

564

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

565

566

* (% style="color:#037691" %)**AT+PRO=3,0 or 3,5 ** (%%)~/~/ hex format or json format

567

568

* (% style="color:#037691" %)**AT+SUBTOPIC=User Defined**

569

570

* (% style="color:#037691" %)**AT+PUBTOPIC=User Defined**

571

572

* (% style="color:#037691" %)**AT+UNAME=<device name> or User Defined**

573

574

* (% style="color:#037691" %)**AT+PWD=<device name> or User Defined**

575

576

* (% style="color:#037691" %)**AT+SERVADDR=8.217.91.207,1883 ** (%%) ~/~/ to set MQTT server address and port

577

578

(% style="color:red" %)**Note: To uplink and downlink via MQTT.fx, we need set the publish topic and subscribe topic different, for example: AT+SUBTOPIC=SE01_SUB & AT+PUBTOPIC=SE01_PUB.**

579

580

[[image:image-20240417180145-2.png||height="434" width="587"]][[ width="584"]]

581

582

**2. **When the node uplink packets, we can observe the data in MQTT.fx.

583

584

[[image:image-20240418144337-1.png||height="709" width="802"]]

585

586

**3. **The downlink command can be successfully sent only when the downlink port is open.

587

588

The downlink port is opened for about 3 seconds after uplink packets are sent.

589

590

Therefore, when we see the node uplink packets in the **Subscribe** window, we need to immediately switch to the **publish** window to publish the **hex format** command.

591

592

[[image:image-20240418150435-3.png||height="582" width="659"]]

593

594

[[image:image-20240418150932-4.png||height="492" width="1061"]]

595

596

(% style="color:red" %)**Note: Users can edit the hex command in advance. When the node uplink, directly click the publish button several times to increase the success rate of command configuration.**

= 5. FAQ =

== 5.1 What is the usage of Multi Sampling and One Uplink? ==

601

602

The NB series has the feature for Multi Sampling and one uplink. See one of them

603

604

[[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/SN50v3-NB_BN-IoT_Sensor_Node_User_Manual/#H2.5Multi-SamplingsandOneuplink>>http://wiki.dragino.com/xwiki/bin/view/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/SN50v3-NB_BN-IoT_Sensor_Node_User_Manual/#H2.5Multi-SamplingsandOneuplink]]

605

606

User can use this feature for below purpose:

607

608

1. **Reduce power consumption**. The NB-IoT transmit power is much more higher than the sensor sampling power. To save battery life, we can sampling often and send in one uplink.

609

1. Give more sampling data points.

610

1. Increase reliable in transmission. For example. If user set

611

1*. **AT+TR=1800** ~/~/ The unit is seconds, and the default is to record data once every 1800 seconds (30 minutes, the minimum can be set to 180 seconds)

612

1*. **AT+NOUD=24** ~/~/ The device uploads 24 sets of recorded data by default. Up to 32 sets of record data can be uploaded.

613

1*. **AT+TDC=7200** ~/~/ Uplink every 2 hours.

614

1*. this will mean each uplink will actually include the 6 uplink data (24 set data which cover 12 hours). So if device doesn't lost 6 continue data. There will not data lost.

615

616

== 5.2 Why the uplink JSON format is not standard? ==

617

618

The json format in uplink packet is not standard Json format. Below is the example. This is to make the payload as short as possible, due to NB-IoT transmit limition, a standard Json is not able to include 32 sets of sensors data with timestamp.

619

620

The firmware version released after 2024, Mar will use change back to use Json format. Detail please check changelog.

621

622

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

623

624

= 6. Trouble Shooting: =

625

626

== 6.1 Checklist for debuging Network Connection issue. Signal Strenght:99 issue. ==

627

628

There are many different providers provide NB-IoT service in the world. They might use different band, different APN & different operator configuration. Which makes connection to NB-IoT network is complicate.

629

630

If end device successfully attached NB-IoT Network, User can normally see the signal strengh as below (between 0~~31)

631

632

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

633

634

If fail to attach network, it will shows signal 99. as below:

635

636

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

637

638

(% class="lead" %)

639

When see this issue, below are the checklist:

640

641

* Does your SIM card support NB-IoT network? If SIM card doesn't not specify support NB-IoT clearly, normally it doesn't support. You need to confirm with your operator.

642

* Do you configure the correct APN? [[Check here for APN settings>>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.1GeneralConfiguretoattachnetwork]].

643

* Do you lock the frequency band? This is the most case we see. [[Explain and Instruction>>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.2SpeedUpNetworkAttachtime]].

644

* Check if the device is attached to Carrier network but reject. (need to check with operator).

645

* Check if the antenna is connected firmly.

646

647

If you have check all above and still fail. please send console log files (as many as possible) to [[support@dragino.com>>mailto:support@dragino.com]] so we can check.

648

649

== 6.2 Issue: "NBIOT did not respond" ==

650

651

(% class="box errormessage" %)

652

(((

653

11:24:22.397 [44596]NBIOT did not respond.

654

11:24:24.315 [46530]NBIOT did not respond.

655

11:24:26.256 [48464]NBIOT did not respond.

656

11:24:28.196 [50398]NBIOT did not respond.

657

11:24:30.115 [52332]NBIOT did not respond.

658

11:24:32.127 [54266]NBIOT did not respond.

659

11:24:32.127 [54299]Restart the module...

660

11:24:39.181 [61332]No response when shutting down

661

)))

662

663

This issue might due to initiate issue for NB-IoT module. In this case, please try:

1) Open Enclosure

2) Power off device by pull out the power on Jumper

668

669

3) Power on device by connect back the power jumper.

670

671

4) push reset button.

672

673

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

674

675

== 6.3 Issue: "Failed to readI MSI number" ==

676

677

(% class="box errormessage" %)

678

(((

679

[18170]Failed to read IMSI:1umber.

680

[20109]Failed to read IMSI numoer.

681

[22048]Failed to read IMSI number.

682

[29842lRestart the module...

683

)))

684

685

Make sure that the SIM card is insert in correct direction and device is power off/on during insert. Here is reference link: [[Insert SIM Card>>||anchor="H2.1GeneralConfiguretoattachnetwork"]].

686

687

== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.4 Why sometime the AT Command is slow in reponse?(%%) ==

688

689

When the MCU is communicating with the NB-IoT module, the MCU response of AT Command will become slower, it might takes several seconds to response.

690

691

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

692

693

== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.5 What is the Downlink Command by the NB device?(%%) ==

694

695

(% data-sider-select-id="bb6e9353-0c3f-473c-938d-4b416c9a03e6" %)

696

=== UDP: ===

697

698

(% data-sider-select-id="14a4790e-7faa-4508-a4dd-7605a53f1cb3" %)

699

Its downlink command is the same as the AT command, but brackets are required.

Example:

{AT+TDC=300}

(% data-sider-select-id="90b80f1a-e924-4c8a-afc5-4429e019a657" %)

=== MQTT: ===

Json：

The Json format in MQTT mode needs to be configured with all commands.

710

If you have configurations that need to be changed, please change them in the template below.

Template:

{

"AT+SERVADDR":"119.91.62.30,1882",

715

"AT+CLIENT":"JwcXKjQBNhQ2JykDDAA5Ahs",

716

"AT+UNAME":"usenamedragino",

717

"AT+PWD":"passworddragino",

"AT+PUBTOPIC":"123",

"AT+SUBTOPIC":"321",

"AT+TDC":"7200",

"AT+INTMOD":"0",

"AT+APN":"NULL",

"AT+5VT":"0",

"AT+PRO":"3,5",

"AT+TR":"900",

"AT+NOUD":"0",

"AT+CSQTIME":"5",

"AT+DNSTIMER":"0",

"AT+TLSMOD":"0,0",

"AT+MQOS":"0",

"AT+TEMPALARM1":"0",

"AT+TEMPALARM2":"10",

"AT+TEMPALARM3":"0"

}

Hex：

MQTT's hex format. Since many commands need to support strings, only a few commands are supported.

739

740

The supported commands are consistent with LoRaWAN's hex commands.

741

Please refer to the following link to obtain the hex format:

742

743

[[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/End%20Device%20AT%20Commands%20and%20Downlink%20Command/>>http://wiki.dragino.com/xwiki/bin/view/Main/End%20Device%20AT%20Commands%20and%20Downlink%20Command/]]

744

745

746

Wiki source code of General Manual for -CB , -CS models

Applications

Navigation