Summary

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

Details

Page properties

Content

...	...	@@ -304,7 +304,6 @@
304	304	* (% style="color:#037691" %)**Password:**(%%) <Your ThingSpeak MQTT Password>
305	305
306	306
307		-
308	308	==== 3.3.2.2 Publish Data to ThingSpeak Channel ====
309	309
310	310
...	...	@@ -345,7 +345,6 @@
345	345	* (% style="color:blue" %)**AT+SUBTOPIC=<YOUR_CHANNEL_ID>**
346	346
347	347
348		-
349	349	==== 3.3.3.2 Uplink Examples ====
350	350
351	351
...	...	@@ -418,7 +418,6 @@
418	418	* (% style="color:blue" %)**S31B-CB-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.
419	419
420	420
421		-
422	422	=== 3.4.1 For device Already has template ===
423	423
424	424	==== 3.4.1.1 Create Device ====
...	...	@@ -579,7 +579,6 @@
579	579	* (% style="color:#037691" %)**AT+PWD=“Your device token”**
580	580
581	581
582		-
583	583	== 3.6 ThingsBoard.Cloud (via MQTT) ==
584	584
585	585	=== 3.6.1 Configure ThingsBoard ===
...	...	@@ -719,7 +719,6 @@
719	719	* (% style="color:#037691" %)**AT+PWD=“Your device token”**
720	720
721	721
722		-
723	723	=== 3.7.2 Simulate with MQTT.fx ===
724	724
725	725
...	...	@@ -846,27 +846,30 @@
846	846
847	847	= 5. GPS positioning function =
848	848
849		-=== 1. Turn on GPS function ===
	844	+== 1. Turn on GPS function ==
850	850
	846	+
851	851	(% class="wikigeneratedid" %)
852		-AT+GPS=1 or 0  ~/~/GPS function on or off
	848	+AT+GPS=1 or 0  ~/~/ GPS function on or off
853	853
854	854
855		-=== 2.Extend the time to turn on GNSS ===
	851	+== 2. Extend the time to turn on GNSS ==
856	856
857		-AT+GNSST=30  ~/~/GPS search for positioning information for 30 seconds
858	858
	854	+AT+GNSST=30  ~/~/ GPS search for positioning information for 30 seconds
859	859
860		-=== 3.Get or set GPS positioning interval in units of hour ===
861	861
862		-AT+GTDC=24  ~/~/The device will activate GPS positioning every 24 hours
	857	+== 3. Get or set GPS positioning interval in units of hour ==
863	863
864	864
865		-= 5. FAQ =
	860	+AT+GTDC=24  ~/~/ The device will activate GPS positioning every 24 hours
866	866
867		-== 5.1 What is the usage of Multi Sampling and One Uplink? ==
868	868
	863	+= 6. FAQ =
869	869
	865	+== 6.1 What is the usage of Multi Sampling and One Uplink? ==
	866	+
	867	+
870	870	The NB series has the feature for Multi Sampling and one uplink. See one of them
871	871
872	872	[[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]]
...	...	@@ -882,10 +882,9 @@
882	882	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.
883	883
884	884
	883	+== 6.2 Why the uplink JSON format is not standard? ==
885	885
886		-== 5.2 Why the uplink JSON format is not standard? ==
887	887
888		-
889	889	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.
890	890
891	891	The firmware version released after 2024, Mar will use change back to use Json format. Detail please check changelog.
...	...	@@ -893,9 +893,9 @@
893	893	[[image:image-20240820112848-57.png]]
894	894
895	895
896		-= 6. Trouble Shooting: =
	893	+= 7. Trouble Shooting: =
897	897
898		-== 6.1 Checklist for debuging Network Connection issue. Signal Strenght:99 issue. ==
	895	+== 7.1 Checklist for debuging Network Connection issue. Signal Strenght:99 issue. ==
899	899
900	900
901	901	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.
...	...	@@ -920,7 +920,7 @@
920	920	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.
921	921
922	922
923		-== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.2 Why sometime the AT Command is slow in reponse?(%%) ==
	920	+== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)7.2 Why sometime the AT Command is slow in reponse?(%%) ==
924	924
925	925
926	926	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.
...	...	@@ -928,7 +928,7 @@
928	928	[[image:image-20240820113015-60.png]]
929	929
930	930
931		-== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.3 What is the Downlink Command by the -CB device?(%%) ==
	928	+== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)7.3 What is the Downlink Command by the -CB device?(%%) ==
932	932
933	933	(% data-sider-select-id="bb6e9353-0c3f-473c-938d-4b416c9a03e6" %)
934	934	=== UDP: ===
...	...	@@ -982,7 +982,7 @@
982	982	[[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/]]
983	983
984	984
985		-== 6.4 What if the signal is good but the domain name resolution fails? ==
	982	+== 7.4 What if the signal is good but the domain name resolution fails? ==
986	986
987	987
988	988	If the domain name resolution fails, first check whether the domain name is correct, users can use their own website domain name resolution tool to verify the domain name.
...	...	@@ -1006,7 +1006,7 @@
1006	1006	[[image:image-20240827150121-5.png||height="476" width="680"]][[image:image-20240827145055-4.png||height="484" width="678"]]
1007	1007
1008	1008
1009		-== 6.5 GPS debugging ==
	1006	+== 7.5 GPS debugging ==
1010	1010
1011	1011
1012	1012	Indoor GPS signal is very weak, **outdoor** positioning is generally recommended.
...	...	@@ -1017,7 +1017,7 @@
1017	1017	[[image:image-20240903104431-10.png||height="291" width="621"]]
1018	1018
1019	1019
1020		-=== 6.5.1 GPS commands ===
	1017	+=== 7.5.1 GPS commands ===
1021	1021
1022	1022
1023	1023	The following are three related AT commands that introduce GPS functions.
...	...	@@ -1069,7 +1069,7 @@
1069	1069	Downlink Payload: **12 00 00 18   **~/~/ AT+GTDC=24
1070	1070
1071	1071
1072		-=== 6.5.2 GPS workflow ===
	1069	+=== 7.5.2 GPS workflow ===
1073	1073
1074	1074
1075	1075	The whole working process after the GPS function is enabled((% style="color:#037691" %)**AT+GPS=1**(%%)) is as follows:
...	...	@@ -1087,7 +1087,7 @@
1087	1087	Only when the node is activated or every (% style="color:#037691" %)**GTDC**(%%) time is reached, the node turns on the GNSS and we can observe the GPS search information through the serial assistant or Bluetooth tool.
1088	1088
1089	1089
1090		-=== 6.5.3 GPS debugging methods ===
	1087	+=== 7.5.3 GPS debugging methods ===
1091	1091
1092	1092
1093	1093	In summary, we can deduce the methods of debugging GPS: