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

55

56

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

57

58

59

Attache to 1NCE card for Australia use:

60

61

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

62

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

63

64

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

65

66

AT+QENG="servingcell"

67

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

68

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

69

70

71

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 =

76

77

== 3.1 General UDP Connection ==

78

79

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

80

81

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

82

83

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

84

85

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

86

87

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

88

89

==== 3.1.2.1 AT Commands ====

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

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

98

99

==== 3.1.2.2 Uplink Example ====

100

101

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

102

103

== 3.2 General COAP Connection ==

104

105

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

106

107

Below are the commands.

108

109

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

110

111

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

112

113

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

114

115

* (% style="color:#037691" %)**AT+URI1=11,"I"** (%%) ~/~/ Configure CoAP Message Options

116

* (% style="color:#037691" %)**AT+URI2=11,"aaa05e26-4d6d-f01b-660e-1d8de4a3bfe1"** (%%) ~/~/ Configure CoAP Message Options

117

118

(% class="wikigeneratedid" %)

119

=== 3.2.1 Uplink Example ===

== 3.2 General MQTT Connection ==

124

125

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

126

127

Below are the commands.

128

129

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

130

131

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

132

133

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

134

135

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

136

137

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

138

139

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

140

141

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

142

143

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

144

145

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

146

147

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

148

149

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

150

151

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

152

153

=== 3.3.1 Get MQTT Credentials ===

154

155

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

156

157

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

158

159

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

160

161

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

162

163

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

164

165

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

166

167

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

168

169

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

170

171

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

172

173

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

174

175

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

176

177

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

178

179

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

180

181

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

182

183

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

184

185

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

186

187

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

188

189

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

190

191

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

192

193

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

194

195

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

196

197

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

198

199

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

200

201

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

202

203

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

204

205

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

206

207

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

208

209

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

210

211

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

212

213

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

214

215

==== 3.3.3.2 Uplink Examples ====

216

217

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

242

243

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.

244

245

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

246

247

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

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

(% class="wikigeneratedid" %)

274

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

275

276

(% class="wikigeneratedid" %)

277

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

278

279

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

280

281

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

282

283

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

284

285

==== 3.4.1.1 Create Device ====

286

287

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

288

289

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

290

291

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

292

293

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

294

295

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

296

297

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

298

299

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

300

301

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

302

303

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

304

305

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

306

307

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

308

309

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

310

311

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

312

313

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

314

315

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

316

317

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

318

319

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

320

321

**Step1: Add a device**

322

323

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

324

325

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

326

327

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

328

329

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

330

331

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

332

333

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

334

335

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

336

337

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

338

339

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

340

341

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

342

343

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

344

345

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

346

347

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

348

349

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

350

351

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

352

353

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

354

355

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

356

357

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

358

359

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

360

361

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

362

363

(% class="lead" %)

364

Use AT command for connecting to DataCake

365

366

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

367

368

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

369

370

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

371

372

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

373

374

Take S31-NB UDP protocol as an example.

375

376

Dragino provides input flow examples for the sensors.

377

378

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

379

380

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

381

382

We can directly import the template.

383

384

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

385

386

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

387

388

Please select the NB95S31B template.

389

390

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

391

392

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

393

394

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

395

396

Successfully imported template.

397

398

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

399

400

Users can set UDP port.

401

402

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

403

404

=== 3.5.2 Simulate Connection ===

405

406

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

407

408

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

409

410

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

411

412

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

413

414

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

415

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

416

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

417

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

418

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

419

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

420

421

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

422

423

=== 3.6.1 Configure ThingsBoard ===

424

425

==== 3.6.1.1 Create Device ====

426

427

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

428

429

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

430

431

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

432

433

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

434

435

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.

436

437

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.

438

439

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

440

441

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

442

443

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

444

445

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

446

447

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

448

449

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

450

451

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

452

453

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

454

455

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

456

457

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

458

459

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

460

461

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

462

463

Consistent with the theme of the node setting.

464

465

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

466

467

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

468

469

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

470

471

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

472

473

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

474

475

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

476

477

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

478

479

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

480

481

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

482

483

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

484

485

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

486

487

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

488

489

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

490

491

Test Uplink by click the button for 1 second

492

493

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

494

495

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

496

497

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

498

499

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

500

501

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

502

503

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.

504

505

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

506

507

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

508

509

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

510

511

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

512

513

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

514

515

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

516

517

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

518

519

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

520

521

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

522

523

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

524

525

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

526

527

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

528

529

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

530

531

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

532

533

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

534

535

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

536

537

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

538

539

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

540

541

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

542

543

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

544

545

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

546

547

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

548

549

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

550

551

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

552

553

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

554

555

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

556

557

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

558

559

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

560

561

=== 3.7.3 tago data ===

562

563

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

564

565

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

566

567

== 3.8 TCP Connection ==

568

569

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

570

571

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

572

573

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

574

575

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

576

577

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

578

579

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

580

581

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

582

583

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

584

585

== 3.9 AWS Connection ==

586

587

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

588

589

= 4. MQTT/UDP/TCP downlink =

590

591

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

592

593

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

594

595

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

596

597

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

598

599

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

600

601

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

602

603

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

604

605

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

606

607

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

608

609

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

610

611

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

612

613

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

614

615

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

616

617

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

618

619

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

620

621

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

622

623

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.

624

625

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

626

627

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

628

629

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

634

635

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

636

637

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

638

639

User can use this feature for below purpose:

640

641

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.

642

1. Give more sampling data points.

643

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

644

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)

645

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

646

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

647

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.

648

649

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

650

651

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.

652

653

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

654

655

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

656

657

= 6. Trouble Shooting: =

658

659

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

660

661

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.

662

663

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

664

665

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

666

667

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

668

669

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

670

671

(% class="lead" %)

672

When see this issue, below are the checklist:

673

674

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

675

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

676

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

677

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

678

* Check if the antenna is connected firmly.

679

680

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.

681

682

683

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

684

685

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.

686

687

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

688

689

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

690

691

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

692

=== UDP: ===

693

694

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

695

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.

706

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

Template:

{

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

711

"AT+CLIENT":"JwcXKjQBNhQ2JykDDAA5Ahs",

712

"AT+UNAME":"usenamedragino",

713

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

735

736

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

737

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

738

739

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

740

741

742

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

Applications

Navigation