Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -634,47 +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		-
660		-* (% style="color:#037691" %)**AT+SERVADDR=8.217.91.207,1883 ** (%%) ~/~/ to set MQTT server address and port
661		-
662		-(% 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.**
663		-
664		-[[image:image-20240417180145-2.png||height="545" width="737"]]
665		-
666		-[[image:image-20240417180737-3.png||height="544" width="738"]]
667		-
668		-
669		-
670		-
671		-
672		-
673		-= 5. FAQ =
674		-
675		-== 5.1 What is the usage of Multi Sampling and One Uplink? ==
676		-
677		-
678	678	The NB series has the feature for Multi Sampling and one uplink. See one of them
679	679
680	680	[[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]]
...	...	@@ -689,7 +689,7 @@
689	689	1*. **AT+TDC=7200**  ~/~/ Uplink every 2 hours.
690	690	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.
691	691
692		-== 5.2 Why the uplink JSON format is not standard? ==
	656	+== 4.2 Why the uplink JSON format is not standard? ==
693	693
694	694
695	695	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.
...	...	@@ -699,9 +699,9 @@
699	699	[[image:image-20240229233154-1.png]]
700	700
701	701
702		-= 6. Trouble Shooting: =
	666	+= 5. Trouble Shooting: =
703	703
704		-== 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. ==
705	705
706	706
707	707	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.
...	...	@@ -728,7 +728,7 @@
728	728	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.
729	729
730	730
731		-== 6.2 Issue: "NBIOT did not respond" ==
	695	+== 5.2 Issue: "NBIOT did not respond" ==
732	732
733	733
734	734	(% class="box errormessage" %)
...	...	@@ -756,7 +756,7 @@
756	756	[[image:image-20240208001740-1.png]]
757	757
758	758
759		-== 6.3 Issue: "Failed to readI MSI number" ==
	723	+== 5.3 Issue: "Failed to readI MSI number" ==
760	760
761	761
762	762	(% class="box errormessage" %)
...	...	@@ -770,7 +770,7 @@
770	770	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"]].
771	771
772	772
773		-== 6.4 Why sometime the AT Command is slow in reponse? ==
	737	+== 5.4 Why sometime the AT Command is slow in reponse? ==
774	774
775	775
776	776	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.