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. Insert the SIM card to Sensor

26

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

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

40

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

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

47

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. User can lock the band to specify band for its operator to make this faster.

48

49

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

50

51

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

52

53

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

54

55

56

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

57

58

59

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

60

61

62

= 3. Configure to connect to different servers =

63

64

== 3.1 General UDP Connection ==

65

66

67

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

68

69

70

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

71

72

73

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

74

75

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

76

77

78

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

79

80

==== 3.1.2.1 AT Commands ====

81

82

83

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

84

85

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

86

87

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

88

89

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

90

91

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

92

93

94

==== 3.1.2.2 Uplink Example ====

95

96

97

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

98

99

100

== 3.2 General MQTT Connection ==

101

102

103

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

104

105

Below are the commands.

106

107

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

108

109

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

110

111

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

112

113

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

114

115

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

116

117

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

118

119

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

120

121

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

122

123

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

124

125

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

126

127

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

128

129

130

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

131

132

=== 3.3.1 Get MQTT Credentials ===

133

134

135

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

136

137

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

138

139

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

140

141

142

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

143

144

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

145

146

147

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

148

149

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

150

151

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

152

153

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

154

155

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

156

157

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

158

159

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

160

161

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

162

163

164

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

165

166

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

167

168

169

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

170

171

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

172

173

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

174

175

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

176

177

178

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

179

180

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

181

182

183

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

184

185

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

186

187

188

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

189

190

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

191

192

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

193

194

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

195

196

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

197

198

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

199

200

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

201

202

==== 3.3.3.2 Uplink Examples ====

203

204

205

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

231

232

233

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.

234

235

236

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

237

238

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

239

240

241

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

242

243

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

244

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

256

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

257

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

258

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

259

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

260

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

261

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

262

263

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

264

265

266

(% class="wikigeneratedid" %)

267

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

268

269

270

(% class="wikigeneratedid" %)

271

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

272

273

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

274

275

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

276

277

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

278

279

==== 3.4.1.1 Create Device ====

280

281

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

282

283

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

284

285

286

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

287

288

289

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

290

291

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

292

293

294

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

295

296

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

297

298

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

299

300

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

301

302

303

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

304

305

**Scan QR Code to get the device info.**

306

307

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

308

309

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

310

311

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

312

313

314

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

315

316

**Step1:Add a device**

317

318

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

319

320

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

321

322

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

323

324

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

325

326

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

327

328

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

329

330

[[image:image-20240129171029-4.png||height="380" width="648"]]

331

332

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

333

334

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

335

336

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

337

338

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

339

340

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

341

342

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

343

344

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

345

346

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

347

348

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

349

350

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

351

352

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

353

354

355

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

356

357

(% class="lead" %)

358

Use AT command for connecting to DataCake

359

360

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

361

362

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

363

364

365

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

366

367

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

368

369

370

Take S31-NB UDP protocol as an example.

371

372

Dragino provides input flow examples for the sensors.

373

374

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

375

376

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

377

378

We can directly import the template.

379

380

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

381

382

383

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

384

385

386

Please select the NB95S31B template.

387

388

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

389

390

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

391

392

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

393

394

395

Successfully imported template.

396

397

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

398

399

400

Users can set UDP port.

401

402

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

403

404

405

=== 3.5.2 Simulate Connection ===

406

407

408

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

409

410

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

411

412

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

413

414

415

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

416

417

418

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

419

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

420

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

421

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

422

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

423

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

424

425

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

426

427

=== 3.6.1 Configure ThingsBoard ===

428

429

==== 3.6.1.1 Create Device ====

430

431

432

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

433

434

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

435

436

437

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

438

439

440

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

441

442

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.

443

444

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.

445

446

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

447

448

449

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

450

451

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

452

453

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

454

455

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

456

457

458

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

459

460

461

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

462

463

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

464

465

466

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

467

468

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

469

470

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

471

472

473

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

474

475

Consistent with the theme of the node setting.

476

477

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

478

479

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

480

481

482

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

483

484

485

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

486

487

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

488

489

490

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

491

492

493

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

494

495

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

496

497

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

498

499

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

500

501

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

502

503

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

504

505

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

506

507

Test Uplink by click the button for 1 second

508

509

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

510

511

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

512

513

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

514

515

516

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

517

518

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

519

520

521

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.

522

523

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

524

525

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

526

527

528

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

529

530

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

531

532

533

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

534

535

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

536

537

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

538

539

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

540

541

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

542

543

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

544

545

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

546

547

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

548

549

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

550

551

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

552

553

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

554

555

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

556

557

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

558

559

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

560

561

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

562

563

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

564

565

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

566

567

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

568

569

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

570

571

572

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

573

574

575

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

576

577

578

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

579

580

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

581

582

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

583

584

585

=== 3.7.3 tago data ===

586

587

588

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

589

590

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

591

592

593

== 3.8 TCP Connection ==

594

595

596

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

597

598

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

599

600

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

601

602

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

603

604

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

605

606

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

607

608

609

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

610

611

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

Wiki source code of General Configure/Commands to Connect to IoT server for -NB & -NS NB-IoT models

Applications

Navigation