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>), example AT+APN=iot.1nce.net

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

44

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

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

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

49

|(% style="background-color:#4f81bd; color:white; width:117px" %)**SIM Provider**|(% style="background-color:#4f81bd; color:white; width:151px" %)**AT+QCGDEFCONT=**|(% style="background-color:#4f81bd; color:white; width:474px" %)**Command Explanation**|(% style="background-color:#4f81bd; color:white; width:135px" %)**Comments**

50

|(% style="width:117px" %)**[[1NCE>>https://1nce.com]]/[[NB card purchased by the customer>>https://1nce.com]]**|(% style="width:151px" %)iot.1nce.net/xxx|(% style="width:474px" %)This command sets the PSD connection settings for PDN connection on power-up. When the MT attaches to the NB-IoT network on power-on, a PDN connection setup is performed. Therefore, PDN connection settings are stored in NVRAM so that they can be used by the modem during the attachment.|(% style="width:135px" %)

51

52

== 2.2 Speed Up Network Attach time ==

53

54

55

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.

56

57

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

58

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

59

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

60

(% style="color:#037691" %)**Global General**(%%) : **AT+QBAND=10,8,20,28,2,4,12,13,66,85,5**

61

62

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

63

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

64

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

65

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

66

67

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

68

69

By default, device will search network for 5 minutes. User can set the time to 10 minutes by (% style="color:#037691" %)**AT+CSQTIME=10 **(%%)so it can search longer.

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

72

73

74

= 3. Configure to connect to different servers =

75

76

== 3.1 General UDP Connection ==

77

78

79

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

80

81

82

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

83

84

85

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

86

87

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

88

89

90

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

91

92

==== 3.1.2.1 AT Commands ====

93

94

95

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

96

97

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

98

99

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

100

101

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

102

103

104

==== 3.1.2.2 Uplink Example ====

105

106

107

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

108

109

110

== 3.2 General MQTT Connection ==

111

112

113

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

114

115

Below are the commands.

116

117

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

118

119

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

120

121

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

122

123

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

124

125

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

126

127

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

128

129

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

130

131

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

132

133

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

134

135

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

136

137

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

138

139

140

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

141

142

=== 3.3.1 Get MQTT Credentials ===

143

144

145

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

146

147

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

148

149

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

150

151

152

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

153

154

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

155

156

157

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

158

159

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

160

161

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

162

163

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

164

165

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

166

167

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

168

169

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

170

171

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

172

173

174

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

175

176

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

177

178

179

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

180

181

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

182

183

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

184

185

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

186

187

188

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

189

190

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

191

192

193

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

194

195

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

196

197

198

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

199

200

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

201

202

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

203

204

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

205

206

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

207

208

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

209

210

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

211

212

==== 3.3.3.2 Uplink Examples ====

213

214

215

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

241

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

246

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

247

248

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

249

250

251

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

252

253

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

254

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

266

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

267

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

268

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

269

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

270

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

271

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

272

273

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

274

275

276

(% class="wikigeneratedid" %)

277

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

278

279

280

(% class="wikigeneratedid" %)

281

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

282

283

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

284

285

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

286

287

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

288

289

==== 3.4.1.1 Create Device ====

290

291

292

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

293

294

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

295

296

297

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

298

299

300

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

301

302

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

303

304

305

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

306

307

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

308

309

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

310

311

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

312

313

314

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

315

316

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

317

318

319

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

320

321

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

322

323

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

324

325

326

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

327

328

329

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

330

331

332

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

333

334

335

**Step1: Add a device**

336

337

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

338

339

340

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

341

342

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

343

344

345

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

346

347

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

348

349

350

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

351

352

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

353

354

355

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

356

357

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

358

359

360

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

361

362

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

363

364

**Due to version update, please use the following decoder for the new version firmware:**

365

[[dragino-end-node-decoder/Datacake-Dragino_NB_New_Version at main · dragino/dragino-end-node-decoder (github.com)>>url:https://github.com/dragino/dragino-end-node-decoder/tree/main/Datacake-Dragino_NB_New_Version]]

366

367

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

368

369

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

370

371

372

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

373

374

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

375

376

377

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

378

379

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

380

381

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

382

383

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

384

385

386

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

(% class="lead" %)

Use AT command for connecting to DataCake

391

392

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

393

394

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

395

396

397

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

398

399

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

400

401

402

Take S31-NB UDP protocol as an example.

403

404

Dragino provides input flow examples for the sensors.

405

406

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

407

408

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

409

410

We can directly import the template.

411

412

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

413

414

415

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

416

417

418

Please select the NB95S31B template.

419

420

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

421

422

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

423

424

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

425

426

427

Successfully imported template.

428

429

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

430

431

432

Users can set UDP port.

433

434

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

435

436

437

=== 3.5.2 Simulate Connection ===

438

439

440

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

441

442

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

443

444

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

445

446

447

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

448

449

450

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

451

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

452

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

453

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

454

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

455

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

456

457

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

458

459

=== 3.6.1 Configure ThingsBoard ===

460

461

==== 3.6.1.1 Create Device ====

462

463

464

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

465

466

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

467

468

469

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

470

471

472

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

473

474

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.

475

476

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.

477

478

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

479

480

481

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

482

483

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

484

485

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

486

487

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

488

489

490

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

491

492

493

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

494

495

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

496

497

498

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

499

500

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

501

502

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

503

504

505

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

506

507

Consistent with the theme of the node setting.

508

509

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

510

511

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

512

513

514

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

515

516

517

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

518

519

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

520

521

522

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

523

524

525

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

526

527

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

528

529

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

530

531

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

532

533

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

534

535

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

536

537

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

538

539

Test Uplink by click the button for 1 second

540

541

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

542

543

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

544

545

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

546

547

548

== 3.7 ThingsBoard.Cloud (via COAP) ==

549

550

=== 3.7.1 Configure ThingsBoard ===

551

552

==== 3.7.1.1 Create Uplink & Downlink Converter ====

553

554

555

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

556

557

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.

558

559

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" %)**“COAP Uplink Converter”**(%%) and select type (% style="color:blue" %)"**Uplink"**(%%). Use debug mode for now.

560

561

[[image:image-20240729141300-1.png||height="552" width="1115"]]

562

563

564

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

565

566

The Downlink converter transforming outgoing RPC message and then the Integration sends it to external COAP broker.

567

568

[[image:image-20240729142505-3.png||height="507" width="1023"]]

569

570

571

==== 3.7.1.2 COAP Integration Setup ====

572

573

574

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" %)**“CoAP Integration”**(%%), select type **COAP **(% style="color:blue" %);

575

576

[[image:image-20240729144058-4.png||height="506" width="1021"]]

577

578

579

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

580

581

[[image:image-20240729150142-5.png||height="507" width="1023"]]

582

583

584

==== 3.7.1.3 Add COAP Integration ====

585

586

587

==== [[image:image-20240729161543-9.png||height="500" width="1009"]] ====

588

589

590

=== 3.7.2 Node Configuration(Example: Connecting to the Thingsboard platform) ===

591

592

==== 3.7.2.1 Instruction Description ====

593

594

595

* AT+PRO=1,0(HEX format uplink) &AT+PRO=1,5(JSON format uplink)

596

* AT+SERVADDR=COAP Server Address,5683

597

598

Example: AT+SERVADDR=int.thingsboard.cloud,5683(The address is automatically generated when the COAP integration is created)

599

600

[[image:image-20240729172305-12.png||height="361" width="624"]]

601

602

Note:The port for the COAP protocol has been fixed to 5683

603

604

605

* AT+URL1=11,(% style="color:red" %)**character length**(%%),"Needs to be consistent with the CoAP endpoint URL in the platform"

606

607

If the module used is (% style="color:red" %)**BC660K, only one **(%%)URL directive needs to be configured,

e.g.

* AT+URL1=11,38, "i/faaaa241f-af4a-b780-4468-c671bb574858"

612

613

[[image:image-20240729172415-13.png||height="401" width="694"]]

614

615

If you are using a (% style="color:red" %)**BG95-M2**(%%) module, you need to configure (% style="color:red" %)**TWO**(%%) URL commands,

e.g.

* AT+URL1=11, "i"

* AT+URL2=11,"faaaa241f-af4a-b780-4468-c671bb574858"

621

622

[[image:image-20240729172500-14.png||height="403" width="700"]]

623

624

625

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

626

627

=== 3.8.1 Create device & Get Credentials ===

628

629

630

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.

631

632

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

633

634

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

635

636

637

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

638

639

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

640

641

642

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

643

644

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

645

646

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

647

648

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

649

650

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

651

652

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

653

654

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

655

656

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

657

658

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

659

660

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

661

662

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

663

664

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

665

666

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

667

668

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

669

670

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

671

672

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

673

674

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

675

676

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

677

678

=== 3.8.2 Simulate with MQTT.fx ===

679

680

681

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

682

683

684

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

685

686

687

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

688

689

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

690

691

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

692

693

694

=== 3.8.3 tago data ===

695

696

697

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

698

699

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

700

701

702

== 3.9 TCP Connection ==

703

704

705

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

706

707

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

708

709

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

710

711

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

712

713

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

714

715

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

716

717

718

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

719

720

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

721

722

723

== 3.10 AWS Connection ==

724

725

726

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

727

728

729

== 3.11 ThingsEye (via MQTT) ==

730

731

=== 3.11.1 Configure ThingsEye ===

732

733

734

==== 3.11.1.1 Create MQTT integration ====

735

736

737

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_NB”**(%%), select type (% style="color:blue" %)**MQTT**;

738

739

[[image:image-20241126175509-1.png||height="518" width="1081"]]

740

741

742

Next, directly select to create a new Uplink data converter and downlink data converter.

743

744

[[image:image-20241126180135-2.png||height="535" width="1092"]]

745

746

[[image:image-20241126180223-3.png||height="518" width="1093"]]

747

748

749

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

750

751

Consistent with the theme of the node setting.

752

753

(% style="color:red" %)**Note: Recommended MQTT broker: lns1.thingseye.io 8883, fixed use. Topic can be changed on their own, but it need to be consistent with the node's publish and subscribe topic.**

754

755

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

756

757

[[image:image-20241126181024-4.png||height="521" width="1081"]]

758

759

760

==== 3.11.1.2 Add credentials to the MQTT integration ====

761

762

763

Click on the MQTT integration you just created.

764

765

[[image:image-20241126181837-5.png||height="365" width="1079"]]

766

767

768

Click the edit icon in the upper right corner to enter the edit mode.

769

770

[[image:image-20241126184523-13.png||height="330" width="1075"]]

771

772

773

(% style="color:blue" %)**Add credential files.**

774

775

Click this [[link>>https://www.dropbox.com/scl/fo/d5s1wf36f4syv30a8laup/AK8FjVpNXYXCWodRnnQ1Hig?rlkey=jrz1ip0f0xwwq5z2m2gu1tuij&e=1&st=kl4caub0&dl=0]] to download the certificates.

776

777

[[image:image-20241126183032-8.png||height="757" width="976"]]

778

779

When the addition is complete, save the Settings.

780

781

[[image:image-20241126184303-12.png||height="284" width="975"]]

782

783

[[image:image-20241126184211-11.png||height="161" width="977"]]

784

785

786

==== 3.11.1.2 Setup uplink and downlink converters ====

787

788

789

First, you need to download the [[**MQTT uplink/downlink JS** **code**>>https://www.dropbox.com/scl/fo/d5s1wf36f4syv30a8laup/AK8FjVpNXYXCWodRnnQ1Hig?rlkey=jrz1ip0f0xwwq5z2m2gu1tuij&e=1&st=kl4caub0&dl=0]].

790

791

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

792

793

The purpose of the decoder function is to parse the incoming data and metadata to a format that ThingsBoard can consume.

794

795

Go to the (% style="color:blue" %)**Integrations center**(%%) -> (% style="color:blue" %)**Data converters**(%%) page, and find that MQTT uplink converter that was newly created when the integration was created.

796

797

[[image:image-20241126184906-14.png||height="424" width="1100"]]

798

799

Enter edit mode and apply **MQTT uplink JS code** to this uplink converter.

800

801

[[image:image-20241126190131-15.png||height="542" width="1103"]]

802

803

804

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

805

806

Go to the (% style="color:blue" %)**Integrations center**(%%) -> (% style="color:blue" %)**Data converters**(%%) page, and find that MQTT downlink converter that was newly created when the integration was created.

807

808

[[image:image-20241126190251-16.png||height="372" width="1113"]]

809

810

Enter edit mode and apply **MQTT downlink JS code** to this downlink converter.

811

812

[[image:image-20241126190737-17.png||height="527" width="1114"]]

813

814

815

=== 3.11.2 Simulate with MQTT.fx ===

816

817

818

[[image:image-20241126191118-18.png||height="605" width="835"]]

819

820

[[image:image-20241126193252-25.png||height="663" width="803"]]

821

822

823

=== 3.6.3 Configure -NB node ===

824

825

826

First you need to configure the certificate to the -NB node. Follow the instructions in this **[[link>>https://wiki.dragino.com/xwiki/bin/view/Dragino%20NB%20device%20connection%20to%20AWS%20platform%20instructions/#H4.1.2Configurecertificate]]** to configure the certificate.

827

828

Screenshot of successful certificate configuration:

829

830

* Configuring the CA Certificate

831

832

[[image:image-20241126192009-19.png||height="431" width="697"]][[image:image-20241126192130-21.png||height="426" width="694"]]

833

834

* Configure client certificate

835

836

[[image:image-20241126192246-22.png||height="397" width="693"]][[image:image-20241126192315-23.png||height="402" width="645"]]

837

838

* Configure client private key

839

840

[[image:image-20241126192415-24.png||height="435" width="737"]]

841

842

843

When the certificate is configured, burn the boot program, burn the working firmware, and then restart the device.

844

845

Then configure the -NB node to connect to the ThingsEye platform:

846

847

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

848

849

* (% style="color:#037691" %)**AT+PRO=3,5 **(%%)** **~/~/ Use MQTT Connection & Json Payload

850

* (% style="color:#037691" %)**AT+SERVADDR=lns1.thingseye.io,8883**

851

* (% style="color:#037691" %)**AT+SUBTOPIC=8899 **(%%)~/~/Consistent with the Topic of MQTT integration created by ThingsEye

852

* (% style="color:#037691" %)**AT+PUBTOPIC=8899 **(%%)~/~/Consistent with the Topic of MQTT integration created by ThingsEye

853

* (% style="color:#037691" %)**AT+CLIENT=NULL**

854

* (% style="color:#037691" %)**AT+UNAME=NULL**

855

* (% style="color:#037691" %)**AT+PWD=NULL**

856

* (% style="color:#037691" %)**AT+TLSMOD=1,0**

857

858

Test Uplink by click the button for 1~~3 seconds, the MQTT integration in ThingsEye allows you to view the data upstream from the device:

859

860

[[image:image-20241126193458-26.png||height="375" width="1012"]]

861

862

[[image:image-20241126193609-27.png||height="424" width="1014"]]

863

864

865

Go to (% style="color:blue" %)**"Device" **(%%) -> (% style="color:blue" %)** "Search Device"**(%%), enter the (% style="color:blue" %)** IMEI**(%%) of the device to find the device.

866

867

[[image:image-20241126194018-28.png||height="318" width="1076"]]

868

869

You can view the data that has just been uplink on the device:

870

871

[[image:image-20241126194123-29.png||height="486" width="1073"]]

= 4. MQTT/UDP/TCP downlink =

876

877

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

878

879

880

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

881

882

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

883

884

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

885

886

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

887

888

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

889

890

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

891

892

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

893

894

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

895

896

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

897

898

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

899

900

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

901

902

903

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

904

905

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

906

907

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

908

909

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

910

911

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.

912

913

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

914

915

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

916

917

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

923

924

925

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

926

927

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

928

929

User can use this feature for below purpose:

930

931

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.

932

1. Give more sampling data points.

933

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

934

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)

935

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

936

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

937

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.

938

939

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

940

941

942

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.

943

944

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

945

946

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

947

948

949

= 6. Trouble Shooting: =

950

951

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

952

953

954

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.

955

956

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

957

958

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

959

960

961

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

962

963

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

(% class="lead" %)

When see this issue, below are the checklist:

968

969

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

970

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

971

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

972

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

973

* Check if the antenna is connected firmly.

974

975

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.

976

977

978

== 6.2 Issue: "NBIOT did not respond" ==

979

980

981

(% class="box errormessage" %)

982

(((

983

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

984

11:24:24.315 [46530]NBIOT did not respond.

985

11:24:26.256 [48464]NBIOT did not respond.

986

11:24:28.196 [50398]NBIOT did not respond.

987

11:24:30.115 [52332]NBIOT did not respond.

988

11:24:32.127 [54266]NBIOT did not respond.

989

11:24:32.127 [54299]Restart the module...

990

11:24:39.181 [61332]No response when shutting down

991

)))

992

993

This issue might due to initiate issue for NB-IoT module. In this case, please try:

1) Open Enclosure

2) Power off device by pull out the power on Jumper

998

999

3) Power on device by connect back the power jumper.

1000

1001

4) push reset button.

1002

1003

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

1004

1005

1006

== 6.3 Issue: "Failed to readI MSI number" ==

1007

1008

1009

(% class="box errormessage" %)

1010

(((

1011

[18170]Failed to read IMSI:1umber.

1012

[20109]Failed to read IMSI numoer.

1013

[22048]Failed to read IMSI number.

1014

[29842lRestart the module...

1015

)))

1016

1017

Make sure that the SIM card is insert in correct direction and device is power off/on during insert. Here is reference link: [[Insert SIM Card>>||anchor="H2.1GeneralConfiguretoattachnetwork"]].

1018

1019

1020

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

1021

1022

1023

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.

1024

1025

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

1026

1027

1028

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

1029

1030

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

1031

=== UDP: ===

1032

1033

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

1034

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.

1046

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

Template:

{

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

1051

"AT+CLIENT":"JwcXKjQBNhQ2JykDDAA5Ahs",

1052

"AT+UNAME":"usenamedragino",

1053

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

1075

1076

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

1077

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

1078

1079

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

1080

1081

1082

== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.6 How to obtain device logs?(%%) ==

1083

1084

1085

* **AT Command: AT** **+GETLOG**

1086

1087

This command can be used to query upstream logs of data packets.

1088

1089

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

1090

1091

1092

== 6.7 How to find the AT Command Password if lost? ==

1093

1094

1095

=== Why can't the password access AT command after upgrade(-NB)? ===

1096

1097

1098

Because the new version of -NB firmware has updated the factory reset function, users can choose to restore all parameters to factory Settings, or keep the password to restore the rest of the parameters to factory Settings.

1099

1100

This update changes the password address of the firmware, so the password will be invalid after the customer upgrades from the old version of firmware (without FDR1 function) to the new version of firmware (with FDR1 function).

1101

1102

Two different restore factory Settings configurations.

1103

1104

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

1105

1106

* (% style="color:#037691; font-weight:bold" %)**AT+FDR**(%%)** **~/~/ Reset Parameters to Factory Default.

1107

* (% style="color:#037691; font-weight:bold" %)**AT+FDR1**(%%)** **~/~/ Reset parameters to factory default values except for passwords.(new)

1108

1109

=== Version Confirmation ===

1110

1111

We are now dividing the **old firmware**(without FDR1 function) with the **new firmware**(with FDR1 function) by whether it contains FDR1 functionality. Please refer to the table:

1112

1113

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

1114

|(% style="background-color:#4f81bd; color:white; width:210px" %)**General Model**|(% style="background-color:#4f81bd; color:white; width:150px" %)(((

1115

**Firmware version**

1116

1117

**(without FDR1 function)**

1118

)))|(% style="background-color:#4f81bd; color:white; width:150px" %)(((

1119

**Firmware version**

1120

1121

**(with FDR1 function)**

1122

)))

1123

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

1124

CPL03-NB, S31-NB, SN50V3-NB, TS01-NB, D20-NB, DS03A-NB, DDS04-NB, DDS45-NB, DDS20-NB, DDS75-NB, LDS12-NB, LDS40-NB, LMS01-NB, MDS120-NB, MDS200-NB, SE01-NB, SPH01-NB;

1125

)))|(% style="width:150px" %)Before V1.2.1|(% style="width:150px" %)After V1.2.1 (including V1.2.1)

1126

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

1127

WL03A-NB, SDI-12-NB;

1128

)))|(% style="width:150px" %)Before V1.0.2|(% style="width:150px" %)(((

1129

After V1.0.8 (including V1.0.2)

1130

)))

1131

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

1132

SW3L-NB, PS-NB;

1133

)))|(% style="width:150px" %)Before V1.0.5|(% style="width:150px" %)(((

1134

After V1.0.5 (including V1.0.5)

1135

)))

1136

|(% style="width:210px" %)RS485-NB|(% style="width:150px" %)Before V1.0.8|(% style="width:150px" %)After V1.0.8 (including V1.0.8)

1137

1138

=== UART connection and firmware update methods ===

1139

1140

1141

Users can query passwords only using the UART interface via the STM32CubeProgrammer.

1142

1143

See **[[UART Connection>>url:http://wiki.dragino.com/xwiki/bin/view/Main/UART%20Access%20for%20LoRa%20ST%20v4%20base%20model/#H2.3UARTConnectionforSN50v3basemotherboard]]**.

1144

1145

update firmware through UART TTL interface :** [[Instruction>>url:http://wiki.dragino.com/xwiki/bin/view/Main/UART_Access_for_NB_ST_BC660K-GL/#H4.2UpdateFirmware28Assumethedevicealreadyhaveabootloader29]]**.

1146

1147

1148

=== query the password via STM32CubeProgrammer ===

1149

1150

1151

Users can use the password address to query the password through STM32CubeProgrammer.

1152

1153

* The password address for old firmware(without FDR1 function) : **0x08019000**

1154

* The password address for new firmware(with FDR1 function) : **0x08025D00**

1155

1156

(% style="color:red" %)**Notice: The password can only be queried after the firmware is run once.**

1157

1158

1159

**Procedure for querying the password(old firmware):**

1160

1161

* After the firmware upgrade is complete, switch back to the **FLASH** and reset the node to **run the firmware once**.

1162

* Then place the switch at the **ISP** and connect to the STM32CubeProgrammer (same as when burning the firmware).

1163

* Click "Device memory", enter **0x08019000** in "Address", and click "Read"

1164

* Find the 0x08019000 address field and then read the current password as shown in the screenshot below.

1165

1166

[[image:http://wiki.dragino.com/xwiki/bin/download/Why%20can%27t%20the%20password%20access%20AT%20command%20after%20upgrade%28-NB%29%3F/WebHome/image-20240827171901-3.png?width=912&height=528&rev=1.1||alt="image-20240827171901-3.png"]]

1167

1168

1169

**Procedure for querying the password(new firmware):**

1170

1171

Refer to [[the old and new firmware division>>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/#HVersionConfirmation]] above, and run the firmware first after updating the firmware.

1172

1173

* After the firmware upgrade is complete, switch back to the **FLASH** and reset the node to **run the new firmware once**.

1174

* Then place the switch at the **ISP** and connect to the STM32CubeProgrammer (same as when burning the firmware).

1175

* Click "Device memory", enter **0x08025D00** in "Address", and click "Read"

1176

* Find the 0x08025D00 address field and then read the current password as shown in the screenshot below.

1177

1178

[[image:http://wiki.dragino.com/xwiki/bin/download/Why%20can%27t%20the%20password%20access%20AT%20command%20after%20upgrade%28-NB%29%3F/WebHome/image-20240827180414-1.png?width=910&height=527&rev=1.1||alt="image-20240827180414-1.png"]]

=== Special case ===

If the user has never changed the password manually, the user cannot find the valid password through the above two password addresses. In this case, the valid password is still the original password on the node box label (**AT+PIN**).

1186

1187

Invalid query screenshot example:

1188

1189

1190

[[image:http://wiki.dragino.com/xwiki/bin/download/Why%20can%27t%20the%20password%20access%20AT%20command%20after%20upgrade%28-NB%29%3F/WebHome/image-20240827181447-4.png?width=889&height=519&rev=1.1||alt="image-20240827181447-4.png"]]

1191

1192

[[image:http://wiki.dragino.com/xwiki/bin/download/Why%20can%27t%20the%20password%20access%20AT%20command%20after%20upgrade%28-NB%29%3F/WebHome/image-20240827181431-3.png?width=892&height=515&rev=1.1||alt="image-20240827181431-3.png"]]

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

Applications

Navigation