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

49

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

50

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

51

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

52

53

== 2.2 Speed Up Network Attach time ==

54

55

56

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.

57

58

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

59

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

60

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

61

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

62

63

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

64

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

65

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

66

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

67

68

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

69

70

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.

71

72

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

73

74

75

= 3. Configure to connect to different servers =

76

77

== 3.1 General UDP Connection ==

78

79

80

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

81

82

83

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

84

85

86

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

87

88

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

89

90

91

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

92

93

==== 3.1.2.1 AT Commands ====

94

95

96

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

97

98

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

99

100

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

101

102

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

103

104

105

==== 3.1.2.2 Uplink Example ====

106

107

108

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

109

110

111

== 3.2 General MQTT Connection ==

112

113

114

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

115

116

Below are the commands.

117

118

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

119

120

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

121

122

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

123

124

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

125

126

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

127

128

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

129

130

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

131

132

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

133

134

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

135

136

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

137

138

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

139

140

141

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

142

143

=== 3.3.1 Get MQTT Credentials ===

144

145

146

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

147

148

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

149

150

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

151

152

153

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

154

155

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

156

157

158

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

159

160

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

161

162

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

163

164

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

165

166

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

167

168

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

169

170

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

171

172

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

173

174

175

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

176

177

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

178

179

180

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

181

182

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

183

184

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

185

186

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

187

188

189

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

190

191

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

192

193

194

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

195

196

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

197

198

199

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

200

201

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

202

203

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

204

205

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

206

207

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

208

209

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

210

211

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

212

213

==== 3.3.3.2 Uplink Examples ====

214

215

216

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

244

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.

245

246

247

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

248

249

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

250

251

252

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

253

254

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

255

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

267

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

268

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

269

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

270

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

271

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

272

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

273

274

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

275

276

277

(% class="wikigeneratedid" %)

278

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

279

280

281

(% class="wikigeneratedid" %)

282

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

283

284

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

285

286

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

287

288

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

289

290

==== 3.4.1.1 Create Device ====

291

292

293

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

294

295

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

296

297

298

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

299

300

301

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

302

303

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

304

305

306

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

307

308

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

309

310

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

311

312

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

313

314

315

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

316

317

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

318

319

320

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

321

322

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

323

324

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

325

326

327

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

328

329

330

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

331

332

333

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

334

335

336

**Step1: Add a device**

337

338

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

339

340

341

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

342

343

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

344

345

346

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

347

348

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

349

350

351

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

352

353

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

354

355

356

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

357

358

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

359

360

361

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

362

363

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

364

365

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

366

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

367

368

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

369

370

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

371

372

373

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

374

375

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

376

377

378

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

379

380

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

381

382

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

383

384

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

385

386

387

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

(% class="lead" %)

Use AT command for connecting to DataCake

392

393

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

394

395

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

396

397

398

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

399

400

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

401

402

403

Take S31-NB UDP protocol as an example.

404

405

Dragino provides input flow examples for the sensors.

406

407

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

408

409

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

410

411

We can directly import the template.

412

413

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

414

415

416

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

417

418

419

Please select the NB95S31B template.

420

421

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

422

423

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

424

425

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

426

427

428

Successfully imported template.

429

430

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

431

432

433

Users can set UDP port.

434

435

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

436

437

438

=== 3.5.2 Simulate Connection ===

439

440

441

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

442

443

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

444

445

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

446

447

448

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

449

450

451

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

452

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

453

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

454

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

455

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

456

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

457

458

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

459

460

=== 3.6.1 Configure ThingsBoard ===

461

462

==== 3.6.1.1 Create Device ====

463

464

465

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

466

467

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

468

469

470

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

471

472

473

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

474

475

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.

476

477

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.

478

479

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

480

481

482

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

483

484

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

485

486

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

487

488

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

489

490

491

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

492

493

494

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

495

496

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

497

498

499

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

500

501

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

502

503

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

504

505

506

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

507

508

Consistent with the theme of the node setting.

509

510

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

511

512

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

513

514

515

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

516

517

518

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

519

520

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

521

522

523

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

524

525

526

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

527

528

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

529

530

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

531

532

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

533

534

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

535

536

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

537

538

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

539

540

Test Uplink by click the button for 1 second

541

542

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

543

544

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

545

546

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

547

548

549

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

550

551

=== 3.7.1 Configure ThingsBoard ===

552

553

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

554

555

556

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

557

558

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.

559

560

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.

561

562

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

563

564

565

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

566

567

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

568

569

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

570

571

572

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

573

574

575

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

576

577

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

578

579

580

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

581

582

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

583

584

585

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

586

587

588

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

589

590

591

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

592

593

==== 3.7.2.1 Instruction Description ====

594

595

596

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

597

* AT+SERVADDR=COAP Server Address,5683

598

599

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

600

601

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

602

603

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

604

605

606

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

607

608

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"

613

614

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

615

616

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"

622

623

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

624

625

626

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

627

628

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

629

630

631

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.

632

633

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

634

635

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

636

637

638

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

639

640

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

641

642

643

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

644

645

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

646

647

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

648

649

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

650

651

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

652

653

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

654

655

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

656

657

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

658

659

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

660

661

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

662

663

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

664

665

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

666

667

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

668

669

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

670

671

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

672

673

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

674

675

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

676

677

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

678

679

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

680

681

682

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

683

684

685

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

686

687

688

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

689

690

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

691

692

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

693

694

695

=== 3.8.3 tago data ===

696

697

698

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

699

700

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

701

702

703

== 3.9 TCP Connection ==

704

705

706

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

707

708

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

709

710

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

711

712

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

713

714

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

715

716

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

717

718

719

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

720

721

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

722

723

724

== 3.10 AWS Connection ==

725

726

727

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

728

729

730

= 4. MQTT/UDP/TCP downlink =

731

732

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

733

734

735

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

736

737

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

738

739

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

740

741

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

742

743

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

744

745

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

746

747

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

748

749

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

750

751

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

752

753

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

754

755

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

756

757

758

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

759

760

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

761

762

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

763

764

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

765

766

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.

767

768

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

769

770

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

771

772

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

778

779

780

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

781

782

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

783

784

User can use this feature for below purpose:

785

786

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.

787

1. Give more sampling data points.

788

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

789

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)

790

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

791

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

792

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.

793

794

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

795

796

797

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.

798

799

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

800

801

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

802

803

804

= 6. Trouble Shooting: =

805

806

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

807

808

809

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.

810

811

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

812

813

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

814

815

816

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

817

818

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

(% class="lead" %)

When see this issue, below are the checklist:

823

824

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

825

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

826

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

827

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

828

* Check if the antenna is connected firmly.

829

830

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.

831

832

833

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

834

835

836

(% class="box errormessage" %)

837

(((

838

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

839

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

840

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

841

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

842

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

843

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

844

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

845

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

846

)))

847

848

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

853

854

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

855

856

4) push reset button.

857

858

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

859

860

861

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

862

863

864

(% class="box errormessage" %)

865

(((

866

[18170]Failed to read IMSI:1umber.

867

[20109]Failed to read IMSI numoer.

868

[22048]Failed to read IMSI number.

869

[29842lRestart the module...

870

)))

871

872

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

873

874

875

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

876

877

878

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.

879

880

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

881

882

883

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

884

885

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

886

=== UDP: ===

887

888

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

889

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.

901

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

Template:

{

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

906

"AT+CLIENT":"JwcXKjQBNhQ2JykDDAA5Ahs",

907

"AT+UNAME":"usenamedragino",

908

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

930

931

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

932

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

933

934

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

935

936

937

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

938

939

940

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

941

942

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

943

944

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

945

946

947

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

948

949

950

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

951

952

953

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.

954

955

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

956

957

Two different restore factory Settings configurations.

958

959

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

960

961

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

962

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

963

964

=== Version Confirmation ===

965

966

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:

967

968

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

969

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

970

**Firmware version**

971

972

**(without FDR1 function)**

973

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

974

**Firmware version**

975

976

**(with FDR1 function)**

977

)))

978

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

979

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;

980

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

981

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

982

WL03A-NB, SDI-12-NB;

983

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

984

After V1.0.8 (including V1.0.2)

985

)))

986

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

987

SW3L-NB, PS-NB;

988

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

989

After V1.0.5 (including V1.0.5)

990

)))

991

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

992

993

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

994

995

996

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

997

998

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

999

1000

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

1001

1002

1003

=== query the password via STM32CubeProgrammer ===

1004

1005

1006

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

1007

1008

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

1009

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

1010

1011

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

1012

1013

1014

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

1015

1016

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

1017

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

1018

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

1019

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

1020

1021

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

1022

1023

1024

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

1025

1026

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.

1027

1028

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

1029

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

1030

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

1031

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

1032

1033

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

1041

1042

Invalid query screenshot example:

1043

1044

1045

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

1046

1047

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