General Manual for -CB , -CS models

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

5

**Table of Contents:**

= 1. The use of this guideline =

10

11

This configure instruction is for Dragino NB-IoT models with -CB or -CS suffix, for example DDS75-CB. These models use the same NB-IoT Module **[[BG95-M2>>https://www.dropbox.com/sh/3ilyaswz4odgaru/AADR86cAgL9UGlmLuEH-UZgla?st=x1ry6v5j&dl=0]]** 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.

12

13

14

= 2. Attach Network =

15

16

== 2.1 General Configure to attach network ==

17

18

To attache end nodes to NB-IoT or LTE-M Network, You need to:

19

20

1. Get a NB-IoT or LTE-M 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-20240602220856-1.png]]

放一张如何插卡图片。

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

33

34

The -CB and -CS models support (% style="color:blue" %)**LTE Cat NB2 and LTE-M (CAT-M1)**(%%), with below frequency band: multiple frequency bands of

35

36

~-~-(% style="color:blue" %)** CAT-NB2: B1/B2/B3/B4/B5/B8/B12/B13/B18/B19/B20/B25/B28/B66/B71/B85 **(%%).

37

38

~-~-(% style="color:blue" %)** CAT-M1: B1/B2/B3/B4/B5/B8/B12/B13/B18/B19/B20/B25/B26/B27/B28/B66/B85 **(%%).

39

40

Make sure you use a the NB-IoT or LTE-M SIM card.

41

42

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

43

|(% 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:406px" %)**NB-IoT Coverage**|(% style="background-color:#4f81bd; color:white; width:351px" %)**LTE-M Coverage**|(% style="background-color:#4f81bd; color:white; width:120px" %)**Comments**

44

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

45

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

46

47

Austria, Belgium, Bulgaria, China, Croatia, Czech Republic, Denmark, Estonia, Finland, Germany, Great Britain, Greece, Hungary, Ireland,Italy, Latvia, Malta, Netherlands, Norway, Portugal, Puerto Rico, Russia, Slovak,Republic, Slovenia, Spain, Sweden, Switzerland, Taiwan, USA, US Virgin Islands

48

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

49

Argentina, Austria, Australia, Belgium, Canada, Denmark,Estonia, Finland, France, Germany, Great Britain, Hungary, Ireland, Japan,Jersey, Korea, Repiblic of, Latvia, Luxembourg, Mexico, Netherlands, New Zealand, Norway, Poland, Puerto Rico, Romania, Spain, Sweden, Switzerland,Taiwan, USA, US Virgin Islands.

50

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

== 2.2 Speed Up Network Attach time ==

56

57

**BG95-M2** supports multi bands (% style="color:blue" %)**in NB-IoT and LTE-M. **(%%) 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**.

58

59

60

Attache to 1NCE card for Australia use:

61

62

* AT+COPS=1,2,"50501",8

63

* AT+QCFG="band",0,0x8000000,0x8000000,1

64

65

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

66

67

AT+QENG="servingcell"

68

+QENG: "servingcell","NOCONN","eMTC","FD

69

D",505,01,90D2C0B,258,9410,28,5,5,901A,-112,-17,-80,10,27

70

71

72

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

= 3. Configure to connect to different servers =

77

78

== 3.1 General UDP Connection ==

79

80

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

81

82

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

83

84

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

85

86

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

87

88

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

89

90

==== 3.1.2.1 AT Commands ====

91

92

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

93

94

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

95

96

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

97

98

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

99

100

==== 3.1.2.2 Uplink Example ====

101

102

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

103

104

== 3.2 General MQTT Connection ==

105

106

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

107

108

Below are the commands.

109

110

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

111

112

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

113

114

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

115

116

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

117

118

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

119

120

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

121

122

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

123

124

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

125

126

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

127

128

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

129

130

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

131

132

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

133

134

=== 3.3.1 Get MQTT Credentials ===

135

136

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

137

138

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

139

140

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

141

142

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

143

144

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

145

146

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

147

148

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

149

150

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

151

152

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

153

154

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

155

156

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

157

158

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

159

160

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

161

162

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

163

164

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

165

166

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

167

168

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

169

170

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

171

172

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

173

174

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

175

176

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

177

178

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

179

180

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

181

182

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

183

184

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

185

186

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

187

188

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

189

190

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

191

192

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

193

194

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

195

196

==== 3.3.3.2 Uplink Examples ====

197

198

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

223

224

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.

225

226

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

227

228

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

229

230

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

231

232

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

233

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

245

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

246

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

247

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

248

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

249

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

250

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

251

252

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

253

254

(% class="wikigeneratedid" %)

255

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

256

257

(% class="wikigeneratedid" %)

258

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

259

260

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

261

262

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

263

264

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

265

266

==== 3.4.1.1 Create Device ====

267

268

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

269

270

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

271

272

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

273

274

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

275

276

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

277

278

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

279

280

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

281

282

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

283

284

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

285

286

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

287

288

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

289

290

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

291

292

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

293

294

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

295

296

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

297

298

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

299

300

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

301

302

**Step1: Add a device**

303

304

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

305

306

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

307

308

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

309

310

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

311

312

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

313

314

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

315

316

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

317

318

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

319

320

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

321

322

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

323

324

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

325

326

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

327

328

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

329

330

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

331

332

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

333

334

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

335

336

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

337

338

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

339

340

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

341

342

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

343

344

(% class="lead" %)

345

Use AT command for connecting to DataCake

346

347

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

348

349

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

350

351

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

352

353

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

354

355

Take S31-NB UDP protocol as an example.

356

357

Dragino provides input flow examples for the sensors.

358

359

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

360

361

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

362

363

We can directly import the template.

364

365

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

366

367

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

368

369

Please select the NB95S31B template.

370

371

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

372

373

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

374

375

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

376

377

Successfully imported template.

378

379

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

380

381

Users can set UDP port.

382

383

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

384

385

=== 3.5.2 Simulate Connection ===

386

387

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

388

389

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

390

391

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

392

393

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

394

395

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

396

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

397

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

398

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

399

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

400

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

401

402

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

403

404

=== 3.6.1 Configure ThingsBoard ===

405

406

==== 3.6.1.1 Create Device ====

407

408

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

409

410

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

411

412

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

413

414

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

415

416

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.

417

418

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.

419

420

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

421

422

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

423

424

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

425

426

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

427

428

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

429

430

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

431

432

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

433

434

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

435

436

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

437

438

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

439

440

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

441

442

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

443

444

Consistent with the theme of the node setting.

445

446

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

447

448

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

449

450

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

451

452

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

453

454

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

455

456

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

457

458

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

459

460

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

461

462

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

463

464

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

465

466

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

467

468

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

469

470

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

471

472

Test Uplink by click the button for 1 second

473

474

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

475

476

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

477

478

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

479

480

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

481

482

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

483

484

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.

485

486

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

487

488

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

489

490

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

491

492

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

493

494

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

495

496

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

497

498

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

499

500

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

501

502

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

503

504

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

505

506

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

507

508

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

509

510

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

511

512

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

513

514

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

515

516

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

517

518

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

519

520

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

521

522

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

523

524

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

525

526

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

527

528

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

529

530

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

531

532

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

533

534

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

535

536

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

537

538

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

539

540

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

541

542

=== 3.7.3 tago data ===

543

544

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

545

546

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

547

548

== 3.8 TCP Connection ==

549

550

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

551

552

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

553

554

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

555

556

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

557

558

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

559

560

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

561

562

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

563

564

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

565

566

== 3.9 AWS Connection ==

567

568

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

569

570

= 4. MQTT/UDP/TCP downlink =

571

572

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

573

574

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

575

576

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

577

578

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

579

580

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

581

582

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

583

584

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

585

586

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

587

588

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

589

590

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

591

592

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

593

594

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

595

596

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

597

598

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

599

600

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

601

602

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

603

604

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.

605

606

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

607

608

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

609

610

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

615

616

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

617

618

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

619

620

User can use this feature for below purpose:

621

622

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.

623

1. Give more sampling data points.

624

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

625

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)

626

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

627

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

628

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.

629

630

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

631

632

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.

633

634

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

635

636

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

637

638

= 6. Trouble Shooting: =

639

640

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

641

642

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.

643

644

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

645

646

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

647

648

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

649

650

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

651

652

(% class="lead" %)

653

When see this issue, below are the checklist:

654

655

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

656

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

657

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

658

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

659

* Check if the antenna is connected firmly.

660

661

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.

662

663

664

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

665

666

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.

667

668

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

669

670

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

671

672

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

673

=== UDP: ===

674

675

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

676

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.

687

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

Template:

{

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

692

"AT+CLIENT":"JwcXKjQBNhQ2JykDDAA5Ahs",

693

"AT+UNAME":"usenamedragino",

694

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

716

717

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

718

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

719

720

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

721

722

723

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

Applications

Navigation