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

== 2.2 Speed Up Network Attach time ==

47

48

49

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.

50

51

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

52

53

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

54

55

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

56

57

58

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

59

60

61

= 3. Configure to connect to different servers =

62

63

== 3.1 General UDP Connection ==

64

65

66

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

67

68

69

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

70

71

72

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

73

74

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

75

76

77

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

78

79

==== 3.1.2.1 AT Commands ====

80

81

82

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

83

84

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

85

86

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

87

88

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

89

90

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

91

92

93

==== 3.1.2.2 Uplink Example ====

94

95

96

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

97

98

99

== 3.2 General MQTT Connection ==

100

101

102

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

103

104

Below are the commands.

105

106

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

107

108

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

109

110

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

111

112

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

113

114

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

115

116

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

117

118

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

119

120

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

121

122

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

123

124

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

125

126

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

127

128

129

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

130

131

=== 3.3.1 Get MQTT Credentials ===

132

133

134

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

135

136

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

137

138

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

139

140

141

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

142

143

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

144

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>

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

163

164

165

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

166

167

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

168

169

170

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

171

172

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

173

174

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

175

176

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

177

178

179

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

180

181

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

182

183

184

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

185

186

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

187

188

189

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

190

191

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

192

193

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

194

195

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

196

197

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

198

199

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

200

201

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

==== 3.3.3.2 Uplink Examples ====

206

207

208

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

234

235

236

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.

237

238

239

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

240

241

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

242

243

244

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

245

246

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

247

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

259

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

260

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

261

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

262

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

263

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

264

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

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

269

270

271

(% class="wikigeneratedid" %)

272

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

273

274

275

(% class="wikigeneratedid" %)

276

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

277

278

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

279

280

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

=== 3.4.1 Create device ===

285

286

287

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

288

289

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

290

291

292

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

293

294

295

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

296

297

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

298

299

300

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

301

302

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

303

304

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

305

306

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

307

308

309

=== 3.4.2 Scan QR code to obtain data ===

310

311

312

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

313

314

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

315

316

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

317

318

319

=== 3.4.2 AT command for connecting to DataCake ===

320

321

322

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

323

324

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

325

326

327

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

328

329

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

330

331

332

Take S31-NB UDP protocol as an example.

333

334

Dragino provides input flow examples for the sensors.

335

336

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

337

338

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

339

340

We can directly import the template.

341

342

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

343

344

345

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

346

347

348

Please select the NB95S31B template.

349

350

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

351

352

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

353

354

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

355

356

357

Successfully imported template.

358

359

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

360

361

362

Users can set UDP port.

363

364

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

365

366

367

=== 3.5.2 Simulate Connection ===

368

369

370

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

371

372

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

373

374

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

375

376

377

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

378

379

380

* (% style="color:blue" %)**AT+PRO=2,0(hex format) or 2,1(json format) **(%%)** **~/~/ Set to UDP Server and Payload

381

382

* (% style="color:blue" %)**AT+SERVADDR=xx.xx.xx.xx,port **(%%)** **~/~/ Set Server IP and port

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

387

388

=== 3.6.1 Configure ThingsBoard ===

389

390

==== 3.6.1.1 Create Device ====

391

392

393

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

394

395

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

396

397

398

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

399

400

401

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

402

403

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.

404

405

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.

406

407

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

408

409

410

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

411

412

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

413

414

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

415

416

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

417

418

419

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

420

421

422

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

423

424

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

425

426

427

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

428

429

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

430

431

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

432

433

434

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

435

436

tb/mqtt-integration-tutorial/sensors~/~/temperature ~-~-> Temperature **固定的? 对的。**

437

438

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

439

440

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

441

442

443

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

444

445

446

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

447

448

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

449

450

451

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

452

453

454

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

455

456

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

457

458

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

459

460

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

461

462

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

463

464

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

465

466

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

467

468

Test Uplink by click the button for 1 second

469

470

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

471

472

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

473

474

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

475

476

477

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

478

479

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

480

481

482

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.

483

484

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

485

486

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

487

488

489

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

490

491

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

492

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

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

533

534

535

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

536

537

538

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

539

540

541

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

542

543

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

544

545

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

546

547

548

=== 3.7.3 tago data ===

549

550

551

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

552

553

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

554

555

556

== 3.8 TCP Connection ==

557

558

559

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

560

561

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

562

563

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

564

565

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

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

570

571

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

572

573

574

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

575

576

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