Skip to Content
Last modified by Kilight Cao on 2025/07/23 16:27
From version 104.3
edited by Xiaoling
on 2023/10/07 10:15
Change comment: There is no comment for this version
To version 178.1
edited by kai
on 2024/07/29 18:02
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Xiaoling
1 +XWiki.kai
Content
... ... @@ -18,12 +18,17 @@
18 18  
19 19  == 2.1 General Configure to attach network ==
20 20  
21 +
21 21  To attache NB-IoT sensors to NB-IoT Network, You need to:
22 22  
23 23  1. Get a NB-IoT SIM card from Service Provider. (Not the same as the SIM card we use in mobile phone)
24 -1. Insert the SIM card to Sensor
25 -1. [[Configure APN>>http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20configure%20APN%20in%20the%20node/]] in the sensor (AT+APN=<APN>)
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
26 26  
30 +[[image:image-20240208102804-1.png||height="286" width="696"]]
31 +
27 27  [[image:image-20230808205045-1.png||height="293" width="438"]]
28 28  
29 29  After doing above, the NB-IoT Sensors should be able to attach to NB-IoT network .
... ... @@ -35,25 +35,33 @@
35 35  |(% style="width:117px" %)**[[1NCE>>https://1nce.com]]**|(% style="width:151px" %)iot.1nce.net|(% style="width:474px" %)(((
36 36  **[[Coverage Reference Link>>https://1nce.com/en-ap/1nce-connect]]**
37 37  
38 -Austria, Belgium, Bulgaria, Croatia, Czech Republic, Denmark, Finland, Germany, Great Britain, Greece, Hungary, Ireland, Italy, Latvia, Malta, Netherlands, Norway, Puerto Rico, Russia, Slovak , Republic, Slovenia, Spain, Sweden, Switzerland, Taiwan, USA, US Virgin Islands
39 -)))|(% style="width:135px" %)
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
40 40  |(% style="width:117px" %)China Mobile|(% style="width:151px" %)No need configure|(% style="width:474px" %)China Mainland, HongKong|(% style="width:135px" %)
41 41  |(% style="width:117px" %)China Telecom|(% style="width:151px" %)ctnb|(% style="width:474px" %)China Mainland|(% style="width:135px" %)
42 42  
43 -(% class="wikigeneratedid" %)
44 -== ==
45 -
46 46  == 2.2 Speed Up Network Attach time ==
47 47  
48 48  
49 -BC660K-GL supports multi bands (% style="color:blue" %)**B1/B2/B3/B4/B5/B8/B12/B13/B14/B17/B18/B19/B20/B25/B28/B66/B70/B85. **(%%) It will search one by one and try to attach, this will take a lot of time and even cause attach fail. User can lock the band to specify band for its operator to make this faster.
51 +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.
50 50  
51 -(% style="color:#037691" %)**AT+QBAND?       ** (%%) ~/~/ Check what is the current used frequency band
53 +(% style="color:#037691" %)**AT+QBAND?       **(%%) ~/~/ Check what is the current used frequency band
54 +(% style="color:#037691" %)**AT+QBAND=1,4    **(%%) ~/~/ Set to use 1 frequency band. Band4
55 +(% style="color:#037691" %)**Europe General**(%%) **AT+QBAND=2,8,20 ** ~/~/ Set to use 2 frequency bands. Band 8 and Band 20
56 +(% style="color:#037691" %)**Global General**(%%) : **AT+QBAND=10,8,20,28,2,4,12,13,66,85,5**
52 52  
53 -(% style="color:#037691" %)**AT+QBAND=1,4    ** (%%) ~/~/ Set to use 1 frequency band. Band4
58 +(% style="color:#037691" %)**Verizon**(%%)** ** AT+QBAND=1,13
59 +(% style="color:#037691" %)**AT&T**(%%)           AT+QBAND=3,12,4,2
60 +(% style="color:#037691" %)**Telstra**(%%)        AT+QBAND=1,28
61 +(% style="color:#037691" %)**Softband**(%%)     AT+QBAND=2,3,8
54 54  
55 -(% style="color:#037691" %)**AT+QBAND=2,8,20**  (%%) ~/~/ Set to use 2 frequency bands. Band 8 and Band 20
63 +After connection is successful, user can use (% style="color:#037691" %)**AT+QENG=0 **(%%) to check which band is actually in used.
56 56  
65 +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.
66 +
67 +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/]]**
68 +
69 +
57 57  = 3. Configure to connect to different servers =
58 58  
59 59  == 3.1 General UDP Connection ==
... ... @@ -67,7 +67,7 @@
67 67  
68 68  We can use PC tool to simulate UDP connection to make sure server works ok.
69 69  
70 -[[image:image-20230802112413-1.png]]
83 +[[image:image-20230802112413-1.png||height="468" width="1024"]]
71 71  
72 72  
73 73  === 3.1.2 Configure NB-IoT Sensor ===
... ... @@ -81,8 +81,6 @@
81 81  
82 82  * (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5601**  (%%) ~/~/  Set UDP server address and port
83 83  
84 -* (% style="color:#037691" %)**AT+CFM=1**    (%%) ~/~/  If the server does not respond, this command is unnecessary
85 -
86 86  [[image:image-20230802112413-2.png]]
87 87  
88 88  
... ... @@ -196,6 +196,7 @@
196 196  
197 197  ==== 3.3.3.2 Uplink Examples ====
198 198  
210 +
199 199  [[image:image-20230816201942-1.png]]
200 200  
201 201  For SE01-NB
... ... @@ -268,15 +268,16 @@
268 268  
269 269  * (% 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.
270 270  
271 -=== 3.4.1 Create device ===
283 +=== 3.4.1 For device Already has template ===
272 272  
285 +==== 3.4.1.1 Create Device ====
273 273  
274 274  (% style="color:blue" %)**Add Device**(%%) in DataCake.
275 275  
276 -[[image:image-20230808162301-1.png||height="473" width="994"]]
289 +[[image:image-20230808162301-1.png||height="453" width="952"]]
277 277  
278 278  
279 -[[image:image-20230808162342-2.png]]
292 +[[image:image-20230808162342-2.png||height="541" width="952"]]
280 280  
281 281  
282 282  (% style="color:blue" %)**Choose the correct model**(%%) from template.
... ... @@ -286,16 +286,18 @@
286 286  
287 287  (% 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.
288 288  
289 -[[image:image-20230808163612-7.png]]
302 +[[image:image-20230808163612-7.png||height="549" width="952"]]
290 290  
291 291  [[image:image-20230808163035-5.png]]
292 292  
293 -[[image:image-20230808163049-6.png]]
306 +[[image:image-20230808163049-6.png||height="544" width="926"]]
294 294  
295 295  
296 -=== 3.4.2 Scan QR code to obtain data ===
309 +=== 3.4.2 For Device already registered in DataCake before shipped ===
297 297  
311 +==== 3.4.2.1 Scan QR Code to get the device info ====
298 298  
313 +
299 299  Users can use their phones or computers to scan QR codes to obtain device data information.
300 300  
301 301  [[image:image-20230808170051-8.png||height="255" width="259"]]
... ... @@ -303,9 +303,69 @@
303 303  [[image:image-20230808170548-9.png]]
304 304  
305 305  
306 -=== 3.4.2 AT command for connecting to DataCake ===
321 +==== 3.4.2.2 Claim Device to User Account ====
307 307  
308 308  
324 +By Default, the device is registered in Dragino's DataCake Account. User can Claim it to his account.
325 +
326 +
327 +=== 3.4.3 Manual Add Decoder in DataCake ( don't use the template in DataCake) ===
328 +
329 +
330 +**Step1: Add a device**
331 +
332 +[[image:image-20240129170024-1.png||height="330" width="900"]]
333 +
334 +
335 +**Step2: Choose your device type,please select dragino NB-IOT device**
336 +
337 +[[image:image-20240129170216-2.png||height="534" width="643"]]
338 +
339 +
340 +**Step3: Choose to create a new device**
341 +
342 +[[image:image-20240129170539-3.png||height="459" width="646"]]
343 +
344 +
345 +**Step4: Fill in the device ID of your NB device**
346 +
347 +[[image:image-20240202111546-1.png||height="378" width="651"]]
348 +
349 +
350 +**Step5: Please select your device plan according to your needs and complete the creation of the device**
351 +
352 +[[image:image-20240129171236-6.png||height="450" width="648"]]
353 +
354 +
355 +**Step6: Please add the decoder at the payload decoder of the device configuration.**
356 +
357 +**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]]
358 +
359 +[[image:image-20240129172056-7.png||height="457" width="816"]]
360 +
361 +[[image:image-20240129173116-9.png||height="499" width="814"]]
362 +
363 +
364 +**Step7: Add the output of the decoder as a field**
365 +
366 +[[image:image-20240129173541-10.png||height="592" width="968"]]
367 +
368 +
369 +**Step8: Customize the dashboard and use fields as parameters of the dashboard**
370 +
371 +[[image:image-20240129174518-11.png||height="147" width="1042"]]
372 +
373 +[[image:image-20240129174657-12.png||height="538" width="916"]]
374 +
375 +[[image:image-20240129174840-13.png||height="536" width="750"]]
376 +
377 +
378 +=== 3.4.4 For device have not configured to connect to DataCake ===
379 +
380 +
381 +(% class="lead" %)
382 +Use AT command for connecting to DataCake
383 +
309 309  (% style="color:blue" %)**AT+PRO=2,0**
310 310  
311 311  (% style="color:blue" %)**AT+SERVADDR=67.207.76.90,4445**
... ... @@ -334,7 +334,7 @@
334 334  
335 335  Please select the NB95S31B template.
336 336  
337 -[[image:image-20230809173310-5.png]]
412 +[[image:image-20230809173310-5.png||height="558" width="926"]]
338 338  
339 339  [[image:image-20230809173438-6.png]]
340 340  
... ... @@ -343,7 +343,7 @@
343 343  
344 344  Successfully imported template.
345 345  
346 -[[image:image-20230809173835-8.png]]
421 +[[image:image-20230809173835-8.png||height="515" width="860"]]
347 347  
348 348  
349 349  Users can set UDP port.
... ... @@ -358,15 +358,19 @@
358 358  
359 359  [[image:image-20230810083934-1.png]]
360 360  
361 -[[image:image-20230810084048-2.png]]
436 +[[image:image-20230810084048-2.png||height="535" width="1052"]]
362 362  
438 +
363 363  === 3.5.3 Configure NB-IoT Sensors ===
364 364  
365 365  
366 -* (% style="color:blue" %)**AT+PRO=2,0(hex format) or 2,1(json format)  **(%%)** **~/~/  Set to UDP Server and  Payload
442 +* (% style="color:#037691" %)**AT+PRO=3,0 or 3,5 ** (%%) **~/~/ hex format or json format**
443 +* (% style="color:#037691" %)**AT+SUBTOPIC=<device name>or User Defined**
444 +* (% style="color:#037691" %)**AT+PUBTOPIC=<device name>or User Defined**
445 +* (% style="color:#037691" %)**AT+CLIENT=<device name> or User Defined**
446 +* (% style="color:#037691" %)**AT+UNAME=<device name> or User Defined**
447 +* (% style="color:#037691" %)**AT+PWD=“Your device token”**
367 367  
368 -* (% style="color:blue" %)**AT+SERVADDR=xx.xx.xx.xx,port   **(%%)** **~/~/  Set Server IP and  port
369 -
370 370  == 3.6 ThingsBoard.Cloud (via MQTT) ==
371 371  
372 372  === 3.6.1 Configure ThingsBoard ===
... ... @@ -376,7 +376,7 @@
376 376  
377 377  Create a New Device in [[ThingsBoard>>url:https://thingsboard.cloud/]]. Record Device Name which is used for MQTT connection.
378 378  
379 -[[image:image-20230802112413-32.png]]
458 +[[image:image-20230802112413-32.png||height="583" width="1066"]]
380 380  
381 381  
382 382  ==== 3.6.1.2 Create Uplink & Downlink Converter ====
... ... @@ -388,7 +388,7 @@
388 388  
389 389  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.
390 390  
391 -[[image:image-20230802112413-33.png||height="732" width="1302"]]
470 +[[image:image-20230802112413-33.png||height="597" width="1061"]]
392 392  
393 393  
394 394  (% style="color:blue" %)**Downlink Converter**
... ... @@ -395,7 +395,7 @@
395 395  
396 396  The Downlink converter transforming outgoing RPC message and then the Integration sends it to external MQTT broke
397 397  
398 -[[image:image-20230802112413-34.png||height="734" width="1305"]]
477 +[[image:image-20230802112413-34.png||height="598" width="1063"]]
399 399  
400 400  (% style="color:red" %)**Note: Our device payload is already human readable data. Therefore, users do not need to write decoders. Simply create by default.**
401 401  
... ... @@ -405,23 +405,23 @@
405 405  
406 406  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**;
407 407  
408 -[[image:image-20230802112413-35.png||height="738" width="1312"]]
487 +[[image:image-20230802112413-35.png||height="597" width="1062"]]
409 409  
410 410  
411 411  * The next steps is to add the recently created uplink and downlink converters;
412 412  
413 -[[image:image-20230802112413-36.png||height="736" width="1308"]]
492 +[[image:image-20230802112413-36.png||height="598" width="1062"]]
414 414  
415 -[[image:image-20230802112413-37.png||height="735" width="1307"]]
494 +[[image:image-20230802112413-37.png||height="598" width="1064"]]
416 416  
417 417  
418 418  (% style="color:blue" %)**Add a topic filter:**
419 419  
420 -tb/mqtt-integration-tutorial/sensors~/~/temperature ~-~-> Temperature  **固定的? 对的。**
499 +Consistent with the theme of the node setting.
421 421  
422 422  You can also select an MQTT QoS level. We use MQTT QoS level 0 (At most once) by default;
423 423  
424 -[[image:image-20230802112413-38.png||height="731" width="1300"]]
503 +[[image:image-20230802112413-38.png||height="598" width="1064"]]
425 425  
426 426  
427 427  === 3.6.2 Simulate with MQTT.fx ===
... ... @@ -429,7 +429,7 @@
429 429  
430 430  [[image:image-20230802112413-39.png]]
431 431  
432 -[[image:image-20230802112413-40.png]]
511 +[[image:image-20230802112413-40.png||height="525" width="980"]]
433 433  
434 434  
435 435  === 3.6.3 Configure NB-IoT Sensor ===
... ... @@ -451,18 +451,94 @@
451 451  
452 452  Test Uplink by click the button for 1 second
453 453  
454 -[[image:image-20230802112413-41.png]]
533 +[[image:image-20230802112413-41.png||height="496" width="828"]]
455 455  
456 456  [[image:image-20230802112413-42.png]]
457 457  
458 -[[image:image-20230802112413-43.png]]
537 +[[image:image-20230802112413-43.png||height="407" width="825"]]
459 459  
460 460  
461 -== 3.7 [[Tago.io>>url:https://admin.tago.io/]] (via MQTT) ==
462 462  
463 -=== 3.7.1 Create device & Get Credentials ===
541 +== 3.7 ThingsBoard.Cloud (via COAP) ==
464 464  
543 +=== 3.7.1 Configure ThingsBoard ===
465 465  
545 +==== 3.7.1.1 Create Uplink & Downlink Converter ====
546 +
547 +
548 +(% style="color:blue" %)**Uplink Converter**
549 +
550 +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.
551 +
552 +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.
553 +
554 +[[image:image-20240729141300-1.png||height="552" width="1115"]]
555 +
556 +
557 +(% style="color:blue" %)**Downlink Converter**
558 +
559 +The Downlink converter transforming outgoing RPC message and then the Integration sends it to external COAP broker.
560 +
561 +[[image:image-20240729142505-3.png||height="507" width="1023"]]
562 +
563 +
564 +==== 3.7.1.2 COAP Integration Setup ====
565 +
566 +
567 +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" %);
568 +
569 +[[image:image-20240729144058-4.png||height="506" width="1021"]]
570 +
571 +
572 +The next steps is to add the recently created uplink converters;
573 +
574 +[[image:image-20240729150142-5.png||height="507" width="1023"]]
575 +
576 +
577 +==== 3.7.1.3 Add COAP Integration ====
578 +
579 +==== [[image:image-20240729161543-9.png||height="500" width="1009"]] ====
580 +
581 +
582 +=== 3.7.2 Node Configuration(Example: Connecting to the Thingsboard platform) ===
583 +
584 +==== 3.7.2.1 Instruction Description ====
585 +
586 +* AT+PRO=1,0(HEX format uplink)  &AT+PRO=1,5(JSON format uplink)
587 +* AT+SERVADDR=COAP Server Address,5683
588 +
589 +Example: AT+SERVADDR=int.thingsboard.cloud,5683(The address is automatically generated when the COAP integration is created)
590 +
591 +[[image:image-20240729172305-12.png||height="361" width="624"]]
592 +
593 +Note:The port for the COAP protocol has been fixed to 5683
594 +
595 +
596 +* AT+URL1=11,(% style="color:red" %)**character length**(%%),"Needs to be consistent with the CoAP endpoint URL in the platform"
597 +
598 +If the module used is (% style="color:red" %)**BC660K, only one **(%%)URL directive needs to be configured,
599 +
600 +e.g.
601 +
602 +* AT+URL1=11,38, "i/faaaa241f-af4a-b780-4468-c671bb574858"
603 +
604 +[[image:image-20240729172415-13.png||height="401" width="694"]]
605 +
606 +If you are using a (% style="color:red" %)**BG95-M2**(%%) module, you need to configure (% style="color:red" %)**TWO**(%%) URL commands,
607 +
608 +e.g.
609 +
610 +* AT+URL1=11, "i"; 
611 +* AT+URL2=11,"/faaaa241f-af4a-b780-4468-c671bb574858"
612 +
613 +[[image:image-20240729172500-14.png||height="403" width="700"]]
614 +
615 +
616 +== 3.8 [[Tago.io>>url:https://admin.tago.io/]] (via MQTT) ==
617 +
618 +=== 3.8.1 Create device & Get Credentials ===
619 +
620 +
466 466  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.
467 467  
468 468  [[image:image-20230802112413-44.png]]
... ... @@ -511,31 +511,31 @@
511 511  
512 512  * (% style="color:#037691" %)**AT+PWD=“Your device token”**
513 513  
514 -=== 3.7.2 Simulate with MQTT.fx ===
669 +=== 3.8.2 Simulate with MQTT.fx ===
515 515  
516 516  
517 517  [[image:image-20230802112413-52.png]]
518 518  
519 519  
520 -[[image:image-20230808105300-2.png]]
675 +[[image:image-20230808105300-2.png||height="553" width="1026"]]
521 521  
522 522  
523 523  Users can run the (% style="color:blue" %)**AT+PRO=3,5**(%%) command, and the payload will be converted to **JSON format**.
524 524  
525 -[[image:image-20230808105217-1.png]]
680 +[[image:image-20230808105217-1.png||height="556" width="1031"]]
526 526  
527 527  [[image:image-20230808105329-3.png]]
528 528  
529 529  
530 -=== 3.7.3 tago data ===
685 +=== 3.8.3 tago data ===
531 531  
532 532  
533 -[[image:image-20230802112413-50.png]]
688 +[[image:image-20230802112413-50.png||height="242" width="1037"]]
534 534  
535 535  [[image:image-20230802112413-51.png||height="184" width="696"]]
536 536  
537 537  
538 -== 3.8 TCP Connection ==
693 +== 3.9 TCP Connection ==
539 539  
540 540  
541 541  (% style="color:blue" %)**AT command:**
... ... @@ -554,3 +554,235 @@
554 554  (% style="color:blue" %)**See result in TCP Server:**
555 555  
556 556  [[image:image-20230807233631-2.png]]
712 +
713 +
714 +== 3.10 AWS Connection ==
715 +
716 +
717 +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]]
718 +
719 +
720 +
721 +
722 += 4. MQTT/UDP/TCP downlink =
723 +
724 +== 4.1 MQTT (via MQTT.fx) ==
725 +
726 +Configure MQTT connections properly and send downlink commands to configure nodes through the Publish function of MQTT.fx//.//
727 +
728 +**1.** Configure node MQTT connection (via MQTT.fx):
729 +
730 +(% style="color:blue" %)**AT command:**
731 +
732 +* (% style="color:#037691" %)**AT+PRO=3,0 or 3,5 ** (%%)~/~/ hex format or json format
733 +
734 +* (% style="color:#037691" %)**AT+SUBTOPIC=User Defined**
735 +
736 +* (% style="color:#037691" %)**AT+PUBTOPIC=User Defined**
737 +
738 +* (% style="color:#037691" %)**AT+UNAME=<device name> or User Defined**
739 +
740 +* (% style="color:#037691" %)**AT+PWD=<device name> or User Defined**
741 +
742 +* (% style="color:#037691" %)**AT+SERVADDR=8.217.91.207,1883 ** (%%) ~/~/ to set MQTT server address and port
743 +
744 +(% 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.**
745 +
746 +[[image:image-20240417180145-2.png||height="434" width="587"]][[image:image-20240417180737-3.png||height="431" width="584"]]
747 +
748 +
749 +**2. **When the node uplink packets, we can observe the data in MQTT.fx.
750 +
751 +[[image:image-20240418144337-1.png||height="709" width="802"]]
752 +
753 +**3. **The downlink command can be successfully sent only when the downlink port is open.
754 +
755 + The downlink port is opened for about 3 seconds after uplink packets are sent.
756 +
757 + 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.
758 +
759 +[[image:image-20240418150435-3.png||height="582" width="659"]]
760 +
761 +[[image:image-20240418150932-4.png||height="492" width="1061"]]
762 +
763 +(% 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.**
764 +
765 +
766 +
767 +
768 +
769 +
770 +
771 += 5. FAQ =
772 +
773 +== 5.1 What is the usage of Multi Sampling and One Uplink? ==
774 +
775 +
776 +The NB series has the feature for Multi Sampling and one uplink. See one of them
777 +
778 +[[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]]
779 +
780 +User can use this feature for below purpose:
781 +
782 +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.
783 +1. Give more sampling data points.
784 +1. Increase reliable in transmission. For example. If user set
785 +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)
786 +1*. **AT+NOUD=24** ~/~/  The device uploads 24 sets of recorded data by default. Up to 32 sets of record data can be uploaded.
787 +1*. **AT+TDC=7200**  ~/~/ Uplink every 2 hours.
788 +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.
789 +
790 +== 5.2 Why the uplink JSON format is not standard? ==
791 +
792 +
793 +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.
794 +
795 +The firmware version released after 2024, Mar will use change back to use Json format. Detail please check changelog.
796 +
797 +[[image:image-20240229233154-1.png]]
798 +
799 +
800 += 6. Trouble Shooting: =
801 +
802 +== 6.1 Checklist for debuging Network Connection issue. Signal Strenght:99 issue. ==
803 +
804 +
805 +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.
806 +
807 +If end device successfully attached NB-IoT Network, User can normally see the signal strengh as below (between 0~~31)
808 +
809 +[[image:image-20240207002003-1.png]]
810 +
811 +
812 +If fail to attach network, it will shows signal 99. as below:
813 +
814 +[[image:image-20240207002129-2.png]]
815 +
816 +
817 +(% class="lead" %)
818 +When see this issue, below are the checklist:
819 +
820 +* 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.
821 +* 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]].
822 +* 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]].
823 +* Check if the device is attached to Carrier network but reject. (need to check with operator).
824 +* Check if the antenna is connected firmly.
825 +
826 +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.
827 +
828 +
829 +== 6.2 Issue: "NBIOT did not respond" ==
830 +
831 +
832 +(% class="box errormessage" %)
833 +(((
834 +11:24:22.397 [44596]NBIOT did not respond.
835 +11:24:24.315 [46530]NBIOT did not respond.
836 +11:24:26.256 [48464]NBIOT did not respond.
837 +11:24:28.196 [50398]NBIOT did not respond.
838 +11:24:30.115 [52332]NBIOT did not respond.
839 +11:24:32.127 [54266]NBIOT did not respond.
840 +11:24:32.127 [54299]Restart the module...
841 +11:24:39.181 [61332]No response when shutting down
842 +)))
843 +
844 +This issue might due to initiate issue for NB-IoT module. In this case, please try:
845 +
846 +1) Open Enclosure
847 +
848 +2) Power off device by pull out the power on Jumper
849 +
850 +3) Power on device by connect back the power jumper.
851 +
852 +4) push reset button.
853 +
854 +[[image:image-20240208001740-1.png]]
855 +
856 +
857 +== 6.3 Issue: "Failed to readI MSI number" ==
858 +
859 +
860 +(% class="box errormessage" %)
861 +(((
862 +[18170]Failed to read IMSI:1umber.
863 +[20109]Failed to read IMSI numoer.
864 +[22048]Failed to read IMSI number.
865 +[29842lRestart the module...
866 +)))
867 +
868 +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"]].
869 +
870 +
871 +== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.4 Why sometime the AT Command is slow in reponse?(%%) ==
872 +
873 +
874 +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.
875 +
876 +[[image:image-20240226111928-1.png]]
877 +
878 +
879 +== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.5 What is the Downlink Command by the NB device?(%%) ==
880 +
881 +(% data-sider-select-id="bb6e9353-0c3f-473c-938d-4b416c9a03e6" %)
882 +=== UDP: ===
883 +
884 +(% data-sider-select-id="14a4790e-7faa-4508-a4dd-7605a53f1cb3" %)
885 +Its downlink command is the same as the AT command, but brackets are required.
886 +Example:
887 +
888 +{AT+TDC=300}
889 +
890 +
891 +(% data-sider-select-id="90b80f1a-e924-4c8a-afc5-4429e019a657" %)
892 +=== MQTT: ===
893 +
894 +Json：
895 +
896 +The Json format in MQTT mode needs to be configured with all commands.
897 +If you have configurations that need to be changed, please change them in the template below.
898 +Template:
899 +
900 +{
901 +"AT+SERVADDR":"119.91.62.30,1882",
902 +"AT+CLIENT":"JwcXKjQBNhQ2JykDDAA5Ahs",
903 +"AT+UNAME":"usenamedragino",
904 +"AT+PWD":"passworddragino",
905 +"AT+PUBTOPIC":"123",
906 +"AT+SUBTOPIC":"321",
907 +"AT+TDC":"7200",
908 +"AT+INTMOD":"0",
909 +"AT+APN":"NULL",
910 +"AT+5VT":"0",
911 +"AT+PRO":"3,5",
912 +"AT+TR":"900",
913 +"AT+NOUD":"0",
914 +"AT+CSQTIME":"5",
915 +"AT+DNSTIMER":"0",
916 +"AT+TLSMOD":"0,0",
917 +"AT+MQOS":"0",
918 +"AT+TEMPALARM1":"0",
919 +"AT+TEMPALARM2":"10",
920 +"AT+TEMPALARM3":"0"
921 +}
922 +
923 +Hex：
924 +
925 +MQTT's hex format. Since many commands need to support strings, only a few commands are supported.
926 +
927 +The supported commands are consistent with LoRaWAN's hex commands.
928 +Please refer to the following link to obtain the hex format:
929 +
930 +[[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/]]
931 +
932 +
933 +== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.6 How to obtain device logs？(%%) ==
934 +
935 +* **AT Command: AT** **+GETLOG**
936 +
937 +This command can be used to query upstream logs of data packets.
938 +
939 +[[image:image-20240701114700-1.png]]
940 +
941 +
942 +
943 +
image-20240129170024-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +52.3 KB
Content
image-20240129170216-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +56.0 KB
Content
image-20240129170539-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +55.0 KB
Content
image-20240129171029-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +36.1 KB
Content
image-20240129171113-5.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +47.2 KB
Content
image-20240129171236-6.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +49.8 KB
Content
image-20240129172056-7.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +69.8 KB
Content
image-20240129172136-8.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +80.4 KB
Content
image-20240129173116-9.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +110.8 KB
Content
image-20240129173541-10.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +95.4 KB
Content
image-20240129174518-11.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +23.2 KB
Content
image-20240129174657-12.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +141.9 KB
Content
image-20240129174840-13.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +92.9 KB
Content
image-20240202111546-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +33.3 KB
Content
image-20240207002003-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Edwin
Size
... ... @@ -1,0 +1,1 @@
1 +22.3 KB
Content
image-20240207002129-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Edwin
Size
... ... @@ -1,0 +1,1 @@
1 +17.9 KB
Content
image-20240208001740-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Edwin
Size
... ... @@ -1,0 +1,1 @@
1 +487.1 KB
Content
image-20240208102804-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Edwin
Size
... ... @@ -1,0 +1,1 @@
1 +507.6 KB
Content
image-20240226111928-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Edwin
Size
... ... @@ -1,0 +1,1 @@
1 +52.0 KB
Content
image-20240229233154-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Edwin
Size
... ... @@ -1,0 +1,1 @@
1 +39.5 KB
Content
image-20240417173549-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +70.3 KB
Content
image-20240417180145-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +104.1 KB
Content
image-20240417180737-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +59.7 KB
Content
image-20240418144337-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +95.1 KB
Content
image-20240418144714-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +50.3 KB
Content
image-20240418150435-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +44.1 KB
Content
image-20240418150932-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +103.4 KB
Content
image-20240701114700-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +291.5 KB
Content
image-20240729141300-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.kai
Size
... ... @@ -1,0 +1,1 @@
1 +176.9 KB
Content
image-20240729142505-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.kai
Size
... ... @@ -1,0 +1,1 @@
1 +202.0 KB
Content
image-20240729144058-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.kai
Size
... ... @@ -1,0 +1,1 @@
1 +140.7 KB
Content
image-20240729150142-5.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.kai
Size
... ... @@ -1,0 +1,1 @@
1 +128.0 KB
Content
image-20240729160802-7.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.kai
Size
... ... @@ -1,0 +1,1 @@
1 +162.8 KB
Content
image-20240729161543-9.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.kai
Size
... ... @@ -1,0 +1,1 @@
1 +166.8 KB
Content
image-20240729172234-11.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.kai
Size
... ... @@ -1,0 +1,1 @@
1 +57.8 KB
Content
image-20240729172305-12.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.kai
Size
... ... @@ -1,0 +1,1 @@
1 +49.3 KB
Content
image-20240729172415-13.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.kai
Size
... ... @@ -1,0 +1,1 @@
1 +54.3 KB
Content
image-20240729172500-14.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.kai
Size
... ... @@ -1,0 +1,1 @@
1 +48.6 KB
Content