Last modified by Mengting Qiu on 2025/03/08 11:33
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
-
Attachments (0 modified, 4 added, 0 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. ting1 +XWiki.Bei - Content
-
... ... @@ -40,8 +40,8 @@ 40 40 |(% style="width:117px" %)**[[1NCE>>https://1nce.com]]**|(% style="width:151px" %)iot.1nce.net|(% style="width:474px" %)((( 41 41 **[[Coverage Reference Link>>https://1nce.com/en-ap/1nce-connect]]** 42 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, US Virgin Islands 44 -)))|(% 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 45 45 |(% style="width:117px" %)China Mobile|(% style="width:151px" %)No need configure|(% style="width:474px" %)China Mainland, HongKong|(% style="width:135px" %) 46 46 |(% style="width:117px" %)China Telecom|(% style="width:151px" %)ctnb|(% style="width:474px" %)China Mainland|(% style="width:135px" %) 47 47 ... ... @@ -642,11 +642,11 @@ 642 642 643 643 Configure MQTT connections properly and send downlink commands to configure nodes through the Publish function of MQTT.fx//.// 644 644 645 -**1.** **Configure node MQTT connection (via MQTT.fx):**645 +**1.** Configure node MQTT connection (via MQTT.fx): 646 646 647 647 (% style="color:blue" %)**AT command:** 648 648 649 -* (% style="color:#037691" %)**AT+PRO=3,0 or 3,5 ** (%%) **~/~/ hex format or json format**649 +* (% style="color:#037691" %)**AT+PRO=3,0 or 3,5 ** (%%)~/~/ hex format or json format 650 650 651 651 * (% style="color:#037691" %)**AT+SUBTOPIC=User Defined** 652 652 ... ... @@ -656,19 +656,35 @@ 656 656 657 657 * (% style="color:#037691" %)**AT+PWD=<device name> or User Defined** 658 658 659 -* (% style="color:#037691" %)**AT+SERVADDR=8.217.91.207,1883 ** (%%) **~/~/ to set MQTT server address and port**659 +* (% style="color:#037691" %)**AT+SERVADDR=8.217.91.207,1883 ** (%%) ~/~/ to set MQTT server address and port 660 660 661 661 (% 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.** 662 662 663 -[[image:image-20240417180145-2.png||height=" 545" width="737"]]663 +[[image:image-20240417180145-2.png||height="434" width="587"]][[image:image-20240417180737-3.png||height="431" width="584"]] 664 664 665 -[[image:image-20240417180737-3.png||height="544" width="738"]] 666 666 666 +**2. **When the node uplink packets, we can observe the data in MQTT.fx. 667 667 668 +[[image:image-20240418144337-1.png||height="709" width="802"]] 668 668 670 +**3. **The downlink command can be successfully sent only when the downlink port is open. 669 669 672 + The downlink port is opened for about 3 seconds after uplink packets are sent. 670 670 674 + 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. 671 671 676 +[[image:image-20240418150435-3.png||height="582" width="659"]] 677 + 678 +[[image:image-20240418150932-4.png||height="492" width="1061"]] 679 + 680 +(% 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.** 681 + 682 + 683 + 684 + 685 + 686 + 687 + 672 672 = 5. FAQ = 673 673 674 674 == 5.1 What is the usage of Multi Sampling and One Uplink? == ... ... @@ -769,9 +769,21 @@ 769 769 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"]]. 770 770 771 771 772 -== 6.4 Why sometime the AT Command is slow in reponse? == 788 +== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.4 Why sometime the AT Command is slow in reponse?(%%) == 773 773 774 774 775 775 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. 776 776 777 777 [[image:image-20240226111928-1.png]] 794 + 795 + 796 +== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.5 What is the Downlink Command by the NB device?(%%) == 797 + 798 + 799 +NB devices use downlink commands in Json format. 800 +Its downlink command is the same as the AT command, but brackets are required. 801 +Example: 802 + 803 +{AT+TDC=300} 804 + 805 +
- 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