General Configure/Commands to Connect to IoT server for -NB & -NS NB-IoT models

1

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

2

**Table of Contents:**

= 1. The use of this guideline =

12

13

14

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.

15

16

17

= 2. Attach Network =

18

19

== 2.1 General Configure to attach network ==

20

21

22

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

23

24

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

25

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

26

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

27

1. Power On End Node

28

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

29

30

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

31

32

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

33

34

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

35

36

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.

37

38

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

39

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

40

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

41

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

42

43

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

44

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

45

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

46

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

47

48

== 2.2 Speed Up Network Attach time ==

49

50

51

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.

52

53

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

54

55

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

56

57

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

58

59

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

60

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

61

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

62

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

63

64

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

65

66

67

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

68

69

70

= 3. Configure to connect to different servers =

71

72

== 3.1 General UDP Connection ==

73

74

75

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

76

77

78

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

79

80

81

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

82

83

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

84

85

86

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

87

88

==== 3.1.2.1 AT Commands ====

89

90

91

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

92

93

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

94

95

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

96

97

* (% style="color:#037691" %)**AT+CFM=1** (%%) ~/~/ If the server does not respond, this command is unnecessary

98

99

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

100

101

102

==== 3.1.2.2 Uplink Example ====

103

104

105

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

106

107

108

== 3.2 General MQTT Connection ==

109

110

111

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

112

113

Below are the commands.

114

115

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

116

117

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

118

119

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

120

121

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

122

123

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

124

125

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

126

127

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

128

129

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

130

131

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

132

133

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

134

135

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

136

137

138

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

139

140

=== 3.3.1 Get MQTT Credentials ===

141

142

143

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

144

145

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

146

147

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

148

149

150

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

151

152

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

153

154

155

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

156

157

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

158

159

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

160

161

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

162

163

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

164

165

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

166

167

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

168

169

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

170

171

172

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

173

174

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

175

176

177

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

178

179

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

180

181

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

182

183

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

184

185

186

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

187

188

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

189

190

191

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

192

193

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

194

195

196

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

197

198

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

199

200

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

201

202

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

203

204

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

205

206

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

207

208

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

209

210

==== 3.3.3.2 Uplink Examples ====

211

212

213

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

239

240

241

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.

242

243

244

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

245

246

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

247

248

249

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

250

251

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

252

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

264

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

265

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

266

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

267

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

268

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

269

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

270

271

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

272

273

274

(% class="wikigeneratedid" %)

275

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

276

277

278

(% class="wikigeneratedid" %)

279

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

280

281

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

282

283

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

284

285

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

286

287

==== 3.4.1.1 Create Device ====

288

289

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

290

291

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

292

293

294

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

295

296

297

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

298

299

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

300

301

302

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

303

304

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

305

306

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

307

308

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

309

310

311

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

312

313

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

314

315

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

316

317

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

318

319

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

320

321

322

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

323

324

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

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

329

330

**Step1:Add a device**

331

332

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

333

334

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

335

336

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

337

338

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

339

340

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

341

342

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

343

344

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

345

346

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

347

348

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

349

350

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

351

352

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

353

354

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

355

356

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

357

358

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

359

360

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

361

362

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

363

364

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

365

366

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

367

368

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

369

370

371

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

372

373

(% class="lead" %)

374

Use AT command for connecting to DataCake

375

376

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

377

378

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

379

380

381

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

382

383

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

384

385

386

Take S31-NB UDP protocol as an example.

387

388

Dragino provides input flow examples for the sensors.

389

390

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

391

392

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

393

394

We can directly import the template.

395

396

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

397

398

399

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

400

401

402

Please select the NB95S31B template.

403

404

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

405

406

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

407

408

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

409

410

411

Successfully imported template.

412

413

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

414

415

416

Users can set UDP port.

417

418

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

419

420

421

=== 3.5.2 Simulate Connection ===

422

423

424

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

425

426

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

427

428

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

429

430

431

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

432

433

434

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

435

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

436

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

437

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

438

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

439

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

440

441

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

442

443

=== 3.6.1 Configure ThingsBoard ===

444

445

==== 3.6.1.1 Create Device ====

446

447

448

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

449

450

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

451

452

453

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

454

455

456

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

457

458

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.

459

460

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.

461

462

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

463

464

465

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

466

467

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

468

469

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

470

471

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

472

473

474

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

475

476

477

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

478

479

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

480

481

482

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

483

484

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

485

486

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

487

488

489

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

490

491

Consistent with the theme of the node setting.

492

493

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

494

495

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

496

497

498

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

499

500

501

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

502

503

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

504

505

506

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

507

508

509

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

510

511

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

512

513

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

514

515

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

516

517

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

518

519

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

520

521

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

522

523

Test Uplink by click the button for 1 second

524

525

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

526

527

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

528

529

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

530

531

532

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

533

534

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

535

536

537

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.

538

539

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

540

541

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

542

543

544

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

545

546

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

547

548

549

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

550

551

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

552

553

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

554

555

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

556

557

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

558

559

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

560

561

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

562

563

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

564

565

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

566

567

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

568

569

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

570

571

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

572

573

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

574

575

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

576

577

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

578

579

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

580

581

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

582

583

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

584

585

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

586

587

588

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

589

590

591

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

592

593

594

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

595

596

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

597

598

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

599

600

601

=== 3.7.3 tago data ===

602

603

604

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

605

606

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

607

608

609

== 3.8 TCP Connection ==

610

611

612

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

613

614

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

615

616

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

617

618

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

619

620

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

621

622

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

623

624

625

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

626

627

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

= 4. FAQ =

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

633

634

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

635

636

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

637

638

User can use this feature for below purpose:

639

640

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.

641

1. Give more sampling data points.

642

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

643

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)

644

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

645

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

646

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.

647

648

= 5. Trouble Shooting: =

649

650

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

651

652

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.

653

654

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

655

656

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

657

658

659

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

660

661

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

(% class="lead" %)

When see this issue, below are the checklist:

666

667

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

668

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

669

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

670

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

671

* Check if the antenna is connected firmly.

672

673

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.

674

675

676

== 5.2 NBIOT did not respond issue. ==

677

678

(% class="box errormessage" %)

679

(((

680

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

681