Skip to Content
Last modified by Mengting Qiu on 2025/07/17 10:51
From version 135.1
edited by Edwin Chen
on 2024/02/08 00:17
Change comment: There is no comment for this version
To version 180.1
edited by Xiaoling
on 2024/08/07 15:10
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Edwin
1 +XWiki.Xiaoling
Content
... ... @@ -22,9 +22,13 @@
22 22  To attache NB-IoT sensors to NB-IoT Network, You need to:
23 23  
24 24  1. Get a NB-IoT SIM card from Service Provider. (Not the same as the SIM card we use in mobile phone)
25 -1. Insert the SIM card to Sensor
26 -1. [[Configure APN>>http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20configure%20APN%20in%20the%20node/]] in the sensor (AT+APN=<APN>)
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
27 27  
30 +[[image:image-20240208102804-1.png||height="286" width="696"]]
31 +
28 28  [[image:image-20230808205045-1.png||height="293" width="438"]]
29 29  
30 30  After doing above, the NB-IoT Sensors should be able to attach to NB-IoT network .
... ... @@ -36,8 +36,8 @@
36 36  |(% style="width:117px" %)**[[1NCE>>https://1nce.com]]**|(% style="width:151px" %)iot.1nce.net|(% style="width:474px" %)(((
37 37  **[[Coverage Reference Link>>https://1nce.com/en-ap/1nce-connect]]**
38 38  
39 -Austria, Belgium, Bulgaria, Croatia, Czech Republic, Denmark, Finland, Germany, Great Britain, Greece, Hungary, Ireland, Italy, Latvia, Malta, Netherlands, Norway, Puerto Rico, Russia, Slovak , Republic, Slovenia, Spain, Sweden, Switzerland, Taiwan, USA, US Virgin Islands
40 -)))|(% style="width:135px" %)
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
41 41  |(% style="width:117px" %)China Mobile|(% style="width:151px" %)No need configure|(% style="width:474px" %)China Mainland, HongKong|(% style="width:135px" %)
42 42  |(% style="width:117px" %)China Telecom|(% style="width:151px" %)ctnb|(% style="width:474px" %)China Mainland|(% style="width:135px" %)
43 43  
... ... @@ -44,13 +44,12 @@
44 44  == 2.2 Speed Up Network Attach time ==
45 45  
46 46  
47 -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.
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.
48 48  
49 49  (% style="color:#037691" %)**AT+QBAND?       **(%%) ~/~/ Check what is the current used frequency band
50 -
51 51  (% style="color:#037691" %)**AT+QBAND=1,4    **(%%) ~/~/ Set to use 1 frequency band. Band4
52 -
53 53  (% 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**
54 54  
55 55  (% style="color:#037691" %)**Verizon**(%%)** ** AT+QBAND=1,13
56 56  (% style="color:#037691" %)**AT&T**(%%)           AT+QBAND=3,12,4,2
... ... @@ -59,6 +59,7 @@
59 59  
60 60  After connection is successful, user can use (% style="color:#037691" %)**AT+QENG=0 **(%%) to check which band is actually in used.
61 61  
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.
62 62  
63 63  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/]]**
64 64  
... ... @@ -90,8 +90,6 @@
90 90  
91 91  * (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5601**  (%%) ~/~/  Set UDP server address and port
92 92  
93 -* (% style="color:#037691" %)**AT+CFM=1**    (%%) ~/~/  If the server does not respond, this command is unnecessary
94 -
95 95  [[image:image-20230802112413-2.png]]
96 96  
97 97  
... ... @@ -162,6 +162,8 @@
162 162  
163 163  * (% style="color:#037691" %)**Password:**(%%) <Your ThingSpeak MQTT Password>
164 164  
167 +
168 +
165 165  ==== 3.3.2.2 Publish Data to ThingSpeak Channel ====
166 166  
167 167  
... ... @@ -203,6 +203,8 @@
203 203  
204 204  * (% style="color:blue" %)**AT+SUBTOPIC=<YOUR_CHANNEL_ID>**
205 205  
210 +
211 +
206 206  ==== 3.3.3.2 Uplink Examples ====
207 207  
208 208  
... ... @@ -264,6 +264,7 @@
264 264  |(% 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" %)
265 265  |(% 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" %)
266 266  
273 +
267 267  == 3.4 [[Datacake>>https://datacake.co/]] ==
268 268  
269 269  
... ... @@ -278,10 +278,13 @@
278 278  
279 279  * (% 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.
280 280  
288 +
289 +
281 281  === 3.4.1 For device Already has template ===
282 282  
283 283  ==== 3.4.1.1 Create Device ====
284 284  
294 +
285 285  (% style="color:blue" %)**Add Device**(%%) in DataCake.
286 286  
287 287  [[image:image-20230808162301-1.png||height="453" width="952"]]
... ... @@ -308,6 +308,7 @@
308 308  
309 309  ==== 3.4.2.1 Scan QR Code to get the device info ====
310 310  
321 +
311 311  Users can use their phones or computers to scan QR codes to obtain device data information.
312 312  
313 313  [[image:image-20230808170051-8.png||height="255" width="259"]]
... ... @@ -317,46 +317,57 @@
317 317  
318 318  ==== 3.4.2.2 Claim Device to User Account ====
319 319  
331 +
320 320  By Default, the device is registered in Dragino's DataCake Account. User can Claim it to his account.
321 321  
322 322  
323 -
324 324  === 3.4.3 Manual Add Decoder in DataCake ( don't use the template in DataCake) ===
325 325  
326 -**Step1:Add a device**
327 327  
338 +**Step1: Add a device**
339 +
328 328  [[image:image-20240129170024-1.png||height="330" width="900"]]
329 329  
330 -**Step2:Choose your device type,please select dragino NB-IOT device**
331 331  
343 +**Step2: Choose your device type,please select dragino NB-IOT device**
344 +
332 332  [[image:image-20240129170216-2.png||height="534" width="643"]]
333 333  
334 -**Step3:Choose to create a new device**
335 335  
348 +**Step3: Choose to create a new device**
349 +
336 336  [[image:image-20240129170539-3.png||height="459" width="646"]]
337 337  
338 -**Step4:Fill in the device ID of your NB device**
339 339  
353 +**Step4: Fill in the device ID of your NB device**
354 +
340 340  [[image:image-20240202111546-1.png||height="378" width="651"]]
341 341  
342 -**Step5:Please select your device plan according to your needs and complete the creation of the device**
343 343  
358 +**Step5: Please select your device plan according to your needs and complete the creation of the device**
359 +
344 344  [[image:image-20240129171236-6.png||height="450" width="648"]]
345 345  
346 -**Step6:Please add the decoder at the payload decoder of the device configuration.**
347 347  
348 -**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 +**Step6: Please add the decoder at the payload decoder of the device configuration.**
349 349  
365 +**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]]
366 +
367 +**Due to version update, please use the following decoder for the new version firmware:**
368 +[[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]]
369 +
350 350  [[image:image-20240129172056-7.png||height="457" width="816"]]
351 351  
352 352  [[image:image-20240129173116-9.png||height="499" width="814"]]
353 353  
354 -**Step6:Add the output of the decoder as a field**
355 355  
375 +**Step7: Add the output of the decoder as a field**
376 +
356 356  [[image:image-20240129173541-10.png||height="592" width="968"]]
357 357  
358 -**Step7:Customize the dashboard and use fields as parameters of the dashboard**
359 359  
380 +**Step8: Customize the dashboard and use fields as parameters of the dashboard**
381 +
360 360  [[image:image-20240129174518-11.png||height="147" width="1042"]]
361 361  
362 362  [[image:image-20240129174657-12.png||height="538" width="916"]]
... ... @@ -366,6 +366,7 @@
366 366  
367 367  === 3.4.4 For device have not configured to connect to DataCake ===
368 368  
391 +
369 369  (% class="lead" %)
370 370  Use AT command for connecting to DataCake
371 371  
... ... @@ -434,6 +434,8 @@
434 434  * (% style="color:#037691" %)**AT+UNAME=<device name> or User Defined**
435 435  * (% style="color:#037691" %)**AT+PWD=“Your device token”**
436 436  
460 +
461 +
437 437  == 3.6 ThingsBoard.Cloud (via MQTT) ==
438 438  
439 439  === 3.6.1 Configure ThingsBoard ===
... ... @@ -525,11 +525,88 @@
525 525  [[image:image-20230802112413-43.png||height="407" width="825"]]
526 526  
527 527  
528 -== 3.7 [[Tago.io>>url:https://admin.tago.io/]] (via MQTT) ==
553 +== 3.7 ThingsBoard.Cloud (via COAP) ==
529 529  
530 -=== 3.7.1 Create device & Get Credentials ===
555 +=== 3.7.1 Configure ThingsBoard ===
531 531  
557 +==== 3.7.1.1 Create Uplink & Downlink Converter ====
532 532  
559 +
560 +(% style="color:blue" %)**Uplink Converter**
561 +
562 +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.
563 +
564 +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.
565 +
566 +[[image:image-20240729141300-1.png||height="552" width="1115"]]
567 +
568 +
569 +(% style="color:blue" %)**Downlink Converter**
570 +
571 +The Downlink converter transforming outgoing RPC message and then the Integration sends it to external COAP broker.
572 +
573 +[[image:image-20240729142505-3.png||height="507" width="1023"]]
574 +
575 +
576 +==== 3.7.1.2 COAP Integration Setup ====
577 +
578 +
579 +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" %);
580 +
581 +[[image:image-20240729144058-4.png||height="506" width="1021"]]
582 +
583 +
584 +The next steps is to add the recently created uplink converters;
585 +
586 +[[image:image-20240729150142-5.png||height="507" width="1023"]]
587 +
588 +
589 +==== 3.7.1.3 Add COAP Integration ====
590 +
591 +
592 +==== [[image:image-20240729161543-9.png||height="500" width="1009"]] ====
593 +
594 +
595 +=== 3.7.2 Node Configuration(Example: Connecting to the Thingsboard platform) ===
596 +
597 +==== 3.7.2.1 Instruction Description ====
598 +
599 +
600 +* AT+PRO=1,0(HEX format uplink)  &AT+PRO=1,5(JSON format uplink)
601 +* AT+SERVADDR=COAP Server Address,5683
602 +
603 +Example: AT+SERVADDR=int.thingsboard.cloud,5683(The address is automatically generated when the COAP integration is created)
604 +
605 +[[image:image-20240729172305-12.png||height="361" width="624"]]
606 +
607 +Note:The port for the COAP protocol has been fixed to 5683
608 +
609 +
610 +* AT+URL1=11,(% style="color:red" %)**character length**(%%),"Needs to be consistent with the CoAP endpoint URL in the platform"
611 +
612 +If the module used is (% style="color:red" %)**BC660K, only one **(%%)URL directive needs to be configured,
613 +
614 +e.g.
615 +
616 +* AT+URL1=11,38, "i/faaaa241f-af4a-b780-4468-c671bb574858"
617 +
618 +[[image:image-20240729172415-13.png||height="401" width="694"]]
619 +
620 +If you are using a (% style="color:red" %)**BG95-M2**(%%) module, you need to configure (% style="color:red" %)**TWO**(%%) URL commands,
621 +
622 +e.g.
623 +
624 +* AT+URL1=11, "i";  
625 +* AT+URL2=11,"/faaaa241f-af4a-b780-4468-c671bb574858"
626 +
627 +[[image:image-20240729172500-14.png||height="403" width="700"]]
628 +
629 +
630 +== 3.8 [[Tago.io>>url:https://admin.tago.io/]] (via MQTT) ==
631 +
632 +=== 3.8.1 Create device & Get Credentials ===
633 +
634 +
533 533  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.
534 534  
535 535  [[image:image-20230802112413-44.png]]
... ... @@ -578,9 +578,11 @@
578 578  
579 579  * (% style="color:#037691" %)**AT+PWD=“Your device token”**
580 580  
581 -=== 3.7.2 Simulate with MQTT.fx ===
582 582  
583 583  
685 +=== 3.8.2 Simulate with MQTT.fx ===
686 +
687 +
584 584  [[image:image-20230802112413-52.png]]
585 585  
586 586  
... ... @@ -594,7 +594,7 @@
594 594  [[image:image-20230808105329-3.png]]
595 595  
596 596  
597 -=== 3.7.3 tago data ===
701 +=== 3.8.3 tago data ===
598 598  
599 599  
600 600  [[image:image-20230802112413-50.png||height="242" width="1037"]]
... ... @@ -602,7 +602,7 @@
602 602  [[image:image-20230802112413-51.png||height="184" width="696"]]
603 603  
604 604  
605 -== 3.8 TCP Connection ==
709 +== 3.9 TCP Connection ==
606 606  
607 607  
608 608  (% style="color:blue" %)**AT command:**
... ... @@ -623,10 +623,62 @@
623 623  [[image:image-20230807233631-2.png]]
624 624  
625 625  
626 -= 4. FAQ =
730 +== 3.10 AWS Connection ==
627 627  
628 -== 4.1 What is the usage of Multi Sampling and One Uplink? ==
629 629  
733 +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]]
734 +
735 +
736 += 4. MQTT/UDP/TCP downlink =
737 +
738 +== 4.1 MQTT (via MQTT.fx) ==
739 +
740 +
741 +Configure MQTT connections properly and send downlink commands to configure nodes through the Publish function of MQTT.fx//.//
742 +
743 +**1.** Configure node MQTT connection (via MQTT.fx):
744 +
745 +(% style="color:blue" %)**AT command:**
746 +
747 +* (% style="color:#037691" %)**AT+PRO=3,0 or 3,5 ** (%%)~/~/ hex format or json format
748 +
749 +* (% style="color:#037691" %)**AT+SUBTOPIC=User Defined**
750 +
751 +* (% style="color:#037691" %)**AT+PUBTOPIC=User Defined**
752 +
753 +* (% style="color:#037691" %)**AT+UNAME=<device name> or User Defined**
754 +
755 +* (% style="color:#037691" %)**AT+PWD=<device name> or User Defined**
756 +
757 +* (% style="color:#037691" %)**AT+SERVADDR=8.217.91.207,1883 ** (%%) ~/~/ to set MQTT server address and port
758 +
759 +(% 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.**
760 +
761 +[[image:image-20240417180145-2.png||height="434" width="587"]][[image:image-20240417180737-3.png||height="431" width="584"]]
762 +
763 +
764 +**2. **When the node uplink packets, we can observe the data in MQTT.fx.
765 +
766 +[[image:image-20240418144337-1.png||height="709" width="802"]]
767 +
768 +**3. **The downlink command can be successfully sent only when the downlink port is open.
769 +
770 + The downlink port is opened for about 3 seconds after uplink packets are sent.
771 +
772 + 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.
773 +
774 +[[image:image-20240418150435-3.png||height="582" width="659"]]
775 +
776 +[[image:image-20240418150932-4.png||height="492" width="1061"]]
777 +
778 +(% 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.**
779 +
780 +
781 += 5. FAQ =
782 +
783 +== 5.1 What is the usage of Multi Sampling and One Uplink? ==
784 +
785 +
630 630  The NB series has the feature for Multi Sampling and one uplink. See one of them
631 631  
632 632  [[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]]
... ... @@ -639,12 +639,23 @@
639 639  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)
640 640  1*. **AT+NOUD=24** ~/~/  The device uploads 24 sets of recorded data by default. Up to 32 sets of record data can be uploaded.
641 641  1*. **AT+TDC=7200**  ~/~/ Uplink every 2 hours.
642 -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.
798 +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.
643 643  
644 -= 5. Trouble Shooting: =
800 +== 5.2 Why the uplink JSON format is not standard? ==
645 645  
646 -== 5.1 Checklist for debuging Network Connection issue. Signal Strenght:99 issue. ==
647 647  
803 +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.
804 +
805 +The firmware version released after 2024, Mar will use change back to use Json format. Detail please check changelog.
806 +
807 +[[image:image-20240229233154-1.png]]
808 +
809 +
810 += 6. Trouble Shooting: =
811 +
812 +== 6.1 Checklist for debuging Network Connection issue. Signal Strenght:99 issue. ==
813 +
814 +
648 648  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.
649 649  
650 650  If end device successfully attached NB-IoT Network, User can normally see the signal strengh as below (between 0~~31)
... ... @@ -669,8 +669,9 @@
669 669  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.
670 670  
671 671  
672 -== 5.2 NBIOT did not respond issue. ==
839 +== 6.2 Issue: "NBIOT did not respond" ==
673 673  
841 +
674 674  (% class="box errormessage" %)
675 675  (((
676 676  11:24:22.397 [44596]NBIOT did not respond.
... ... @@ -694,3 +694,93 @@
694 694  4) push reset button.
695 695  
696 696  [[image:image-20240208001740-1.png]]
865 +
866 +
867 +== 6.3 Issue: "Failed to readI MSI number" ==
868 +
869 +
870 +(% class="box errormessage" %)
871 +(((
872 +[18170]Failed to read IMSI:1umber.
873 +[20109]Failed to read IMSI numoer.
874 +[22048]Failed to read IMSI number.
875 +[29842lRestart the module...
876 +)))
877 +
878 +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"]].
879 +
880 +
881 +== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.4 Why sometime the AT Command is slow in reponse?(%%) ==
882 +
883 +
884 +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.
885 +
886 +[[image:image-20240226111928-1.png]]
887 +
888 +
889 +== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.5 What is the Downlink Command by the NB device?(%%) ==
890 +
891 +(% data-sider-select-id="bb6e9353-0c3f-473c-938d-4b416c9a03e6" %)
892 +=== UDP: ===
893 +
894 +(% data-sider-select-id="14a4790e-7faa-4508-a4dd-7605a53f1cb3" %)
895 +Its downlink command is the same as the AT command, but brackets are required.
896 +Example:
897 +
898 +{AT+TDC=300}
899 +
900 +
901 +(% data-sider-select-id="90b80f1a-e924-4c8a-afc5-4429e019a657" %)
902 +=== MQTT: ===
903 +
904 +Json：
905 +
906 +The Json format in MQTT mode needs to be configured with all commands.
907 +If you have configurations that need to be changed, please change them in the template below.
908 +Template:
909 +
910 +{
911 +"AT+SERVADDR":"119.91.62.30,1882",
912 +"AT+CLIENT":"JwcXKjQBNhQ2JykDDAA5Ahs",
913 +"AT+UNAME":"usenamedragino",
914 +"AT+PWD":"passworddragino",
915 +"AT+PUBTOPIC":"123",
916 +"AT+SUBTOPIC":"321",
917 +"AT+TDC":"7200",
918 +"AT+INTMOD":"0",
919 +"AT+APN":"NULL",
920 +"AT+5VT":"0",
921 +"AT+PRO":"3,5",
922 +"AT+TR":"900",
923 +"AT+NOUD":"0",
924 +"AT+CSQTIME":"5",
925 +"AT+DNSTIMER":"0",
926 +"AT+TLSMOD":"0,0",
927 +"AT+MQOS":"0",
928 +"AT+TEMPALARM1":"0",
929 +"AT+TEMPALARM2":"10",
930 +"AT+TEMPALARM3":"0"
931 +}
932 +
933 +Hex：
934 +
935 +MQTT's hex format. Since many commands need to support strings, only a few commands are supported.
936 +
937 +The supported commands are consistent with LoRaWAN's hex commands.
938 +Please refer to the following link to obtain the hex format:
939 +
940 +[[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/]]
941 +
942 +
943 +== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.6 How to obtain device logs?(%%) ==
944 +
945 +
946 +* **AT Command: AT** **+GETLOG**
947 +
948 +This command can be used to query upstream logs of data packets.
949 +
950 +[[image:image-20240701114700-1.png]]
951 +
952 +
953 +
954 +
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