Summary

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

Details

Page properties

Content

...	...	@@ -304,6 +304,7 @@
304	304	* (% style="color:#037691" %)**Password:**(%%) <Your ThingSpeak MQTT Password>
305	305
306	306
	307	+
307	307	==== 3.3.2.2 Publish Data to ThingSpeak Channel ====
308	308
309	309
...	...	@@ -344,6 +344,7 @@
344	344	* (% style="color:blue" %)**AT+SUBTOPIC=<YOUR_CHANNEL_ID>**
345	345
346	346
	348	+
347	347	==== 3.3.3.2 Uplink Examples ====
348	348
349	349
...	...	@@ -416,6 +416,7 @@
416	416	* (% 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.
417	417
418	418
	421	+
419	419	=== 3.4.1 For device Already has template ===
420	420
421	421	==== 3.4.1.1 Create Device ====
...	...	@@ -576,6 +576,7 @@
576	576	* (% style="color:#037691" %)**AT+PWD=“Your device token”**
577	577
578	578
	582	+
579	579	== 3.6 ThingsBoard.Cloud (via MQTT) ==
580	580
581	581	=== 3.6.1 Configure ThingsBoard ===
...	...	@@ -715,6 +715,7 @@
715	715	* (% style="color:#037691" %)**AT+PWD=“Your device token”**
716	716
717	717
	722	+
718	718	=== 3.7.2 Simulate with MQTT.fx ===
719	719
720	720
...	...	@@ -841,30 +841,27 @@
841	841
842	842	= 5. GPS positioning function =
843	843
844		-== 1. Turn on GPS function ==
	849	+=== 1. Turn on GPS function ===
845	845
846		-
847	847	(% class="wikigeneratedid" %)
848		-AT+GPS=1 or 0  ~/~/ GPS function on or off
	852	+AT+GPS=1 or 0  ~/~/GPS function on or off
849	849
850	850
851		-== 2. Extend the time to turn on GNSS ==
	855	+=== 2.Extend the time to turn on GNSS ===
852	852
	857	+AT+GNSST=30  ~/~/GPS search for positioning information for 30 seconds
853	853
854		-AT+GNSST=30  ~/~/ GPS search for positioning information for 30 seconds
855	855
	860	+=== 3.Get or set GPS positioning interval in units of hour ===
856	856
857		-== 3. Get or set GPS positioning interval in units of hour ==
	862	+AT+GTDC=24  ~/~/The device will activate GPS positioning every 24 hours
858	858
859	859
860		-AT+GTDC=24  ~/~/ The device will activate GPS positioning every 24 hours
	865	+= 5. FAQ =
861	861
	867	+== 5.1 What is the usage of Multi Sampling and One Uplink? ==
862	862
863		-= 6. FAQ =
864	864
865		-== 6.1 What is the usage of Multi Sampling and One Uplink? ==
866		-
867		-
868	868	The NB series has the feature for Multi Sampling and one uplink. See one of them
869	869
870	870	[[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]]
...	...	@@ -880,9 +880,10 @@
880	880	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.
881	881
882	882
883		-== 6.2 Why the uplink JSON format is not standard? ==
884	884
	886	+== 5.2 Why the uplink JSON format is not standard? ==
885	885
	888	+
886	886	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.
887	887
888	888	The firmware version released after 2024, Mar will use change back to use Json format. Detail please check changelog.
...	...	@@ -890,9 +890,9 @@
890	890	[[image:image-20240820112848-57.png]]
891	891
892	892
893		-= 7. Trouble Shooting: =
	896	+= 6. Trouble Shooting: =
894	894
895		-== 7.1 Checklist for debuging Network Connection issue. Signal Strenght:99 issue. ==
	898	+== 6.1 Checklist for debuging Network Connection issue. Signal Strenght:99 issue. ==
896	896
897	897
898	898	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.
...	...	@@ -917,7 +917,7 @@
917	917	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.
918	918
919	919
920		-== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)7.2 Why sometime the AT Command is slow in reponse?(%%) ==
	923	+== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.2 Why sometime the AT Command is slow in reponse?(%%) ==
921	921
922	922
923	923	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.
...	...	@@ -925,7 +925,7 @@
925	925	[[image:image-20240820113015-60.png]]
926	926
927	927
928		-== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)7.3 What is the Downlink Command by the -CB device?(%%) ==
	931	+== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.3 What is the Downlink Command by the -CB device?(%%) ==
929	929
930	930	(% data-sider-select-id="bb6e9353-0c3f-473c-938d-4b416c9a03e6" %)
931	931	=== UDP: ===
...	...	@@ -979,7 +979,7 @@
979	979	[[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/]]
980	980
981	981
982		-== 7.4 What if the signal is good but the domain name resolution fails? ==
	985	+== 6.4 What if the signal is good but the domain name resolution fails? ==
983	983
984	984
985	985	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.
...	...	@@ -1003,7 +1003,7 @@
1003	1003	[[image:image-20240827150121-5.png||height="476" width="680"]][[image:image-20240827145055-4.png||height="484" width="678"]]
1004	1004
1005	1005
1006		-== 7.5 GPS debugging ==
	1009	+== 6.5 GPS debugging ==
1007	1007
1008	1008
1009	1009	Indoor GPS signal is very weak, **outdoor** positioning is generally recommended.
...	...	@@ -1014,7 +1014,7 @@
1014	1014	[[image:image-20240903104431-10.png||height="291" width="621"]]
1015	1015
1016	1016
1017		-=== 7.5.1 GPS commands ===
	1020	+=== 6.5.1 GPS commands ===
1018	1018
1019	1019
1020	1020	The following are three related AT commands that introduce GPS functions.
...	...	@@ -1066,7 +1066,7 @@
1066	1066	Downlink Payload: **12 00 00 18   **~/~/ AT+GTDC=24
1067	1067
1068	1068
1069		-=== 7.5.2 GPS workflow ===
	1072	+=== 6.5.2 GPS workflow ===
1070	1070
1071	1071
1072	1072	The whole working process after the GPS function is enabled((% style="color:#037691" %)**AT+GPS=1**(%%)) is as follows:
...	...	@@ -1084,7 +1084,7 @@
1084	1084	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.
1085	1085
1086	1086
1087		-=== 7.5.3 GPS debugging methods ===
	1090	+=== 6.5.3 GPS debugging methods ===
1088	1088
1089	1089
1090	1090	In summary, we can deduce the methods of debugging GPS: