Skip to Content
Last modified by Mengting Qiu on 2025/07/03 18:55
From version 155.1
edited by Mengting Qiu
on 2024/04/18 14:02
Change comment: There is no comment for this version
To version 152.1
edited by Mengting Qiu
on 2024/04/17 18:01
Change comment: Uploaded new attachment "image-20240417180145-2.png", version {1}

Summary

Details

Page properties
Content
... ... @@ -634,46 +634,11 @@
634 634  [[image:image-20230807233631-2.png]]
635 635  
636 636  
637 += 4. FAQ =
637 637  
639 +== 4.1 What is the usage of Multi Sampling and One Uplink? ==
638 638  
639 -= 4. MQTT/UDP/TCP downlink =
640 640  
641 -== 4.1 MQTT (via MQTT.fx) ==
642 -
643 -Configure MQTT connections properly and send downlink commands to configure nodes through the Publish function of MQTT.fx//.//
644 -
645 -**1.** **Configure node MQTT connection (via MQTT.fx):**
646 -
647 -(% style="color:blue" %)**AT command:**
648 -
649 -* (% style="color:#037691" %)**AT+PRO=3,0 or 3,5 ** (%%) **~/~/ hex format or json format**
650 -
651 -* (% style="color:#037691" %)**AT+SUBTOPIC=User Defined**
652 -
653 -* (% style="color:#037691" %)**AT+PUBTOPIC=User Defined**
654 -
655 -* (% style="color:#037691" %)**AT+UNAME=<device name> or User Defined**
656 -
657 -* (% style="color:#037691" %)**AT+PWD=<device name> or User Defined**
658 -
659 -* (% style="color:#037691" %)**AT+SERVADDR=8.217.91.207,1883 ** (%%) **~/~/ to set MQTT server address and port**
660 -
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 -
663 -[[image:image-20240417180145-2.png||height="545" width="737"]]
664 -
665 -[[image:image-20240417180737-3.png||height="544" width="738"]]
666 -
667 -
668 -
669 -
670 -
671 -
672 -= 5. FAQ =
673 -
674 -== 5.1 What is the usage of Multi Sampling and One Uplink? ==
675 -
676 -
677 677  The NB series has the feature for Multi Sampling and one uplink. See one of them
678 678  
679 679  [[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]]
... ... @@ -688,7 +688,7 @@
688 688  1*. **AT+TDC=7200**  ~/~/ Uplink every 2 hours.
689 689  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.
690 690  
691 -== 5.2 Why the uplink JSON format is not standard? ==
656 +== 4.2 Why the uplink JSON format is not standard? ==
692 692  
693 693  
694 694  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.
... ... @@ -698,9 +698,9 @@
698 698  [[image:image-20240229233154-1.png]]
699 699  
700 700  
701 -= 6. Trouble Shooting: =
666 += 5. Trouble Shooting: =
702 702  
703 -== 6.1 Checklist for debuging Network Connection issue. Signal Strenght:99 issue. ==
668 +== 5.1 Checklist for debuging Network Connection issue. Signal Strenght:99 issue. ==
704 704  
705 705  
706 706  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.
... ... @@ -727,7 +727,7 @@
727 727  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.
728 728  
729 729  
730 -== 6.2 Issue: "NBIOT did not respond" ==
695 +== 5.2 Issue: "NBIOT did not respond" ==
731 731  
732 732  
733 733  (% class="box errormessage" %)
... ... @@ -755,7 +755,7 @@
755 755  [[image:image-20240208001740-1.png]]
756 756  
757 757  
758 -== 6.3 Issue: "Failed to readI MSI number" ==
723 +== 5.3 Issue: "Failed to readI MSI number" ==
759 759  
760 760  
761 761  (% class="box errormessage" %)
... ... @@ -769,7 +769,7 @@
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? ==
737 +== 5.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.
image-20240417180737-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -59.7 KB
Content