Summary

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

Details

Page properties

Content

...	...	@@ -356,6 +356,8 @@
356	356	* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/ to set UDP server address and port
357	357	* (% style="color:blue" %)**AT+CFM=1       ** (%%) ~/~/ If the server does not respond, this command is unnecessary
358	358
	359	+
	360	+
359	359	[[image:1657352391268-297.png]]
360	360
361	361
...	...	@@ -365,6 +365,7 @@
365	365
366	366	=== 2.2.7  Use MQTT protocol to uplink data ===
367	367
	370	+
368	368	N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption.
369	369
370	370	* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
...	...	@@ -375,11 +375,14 @@
375	375	* (% style="color:blue" %)**AT+PUBTOPIC=f9527                               **(%%)~/~/Set the sending topic of MQTT
376	376	* (% style="color:blue" %)**AT+SUBTOPIC=Ns9527          **(%%) ~/~/Set the subscription topic of MQTT
377	377
	381	+
	382	+
378	378	[[image:1657352634421-276.png]]
379	379
380	380
381	381	[[image:1657352645687-385.png]]
382	382
	388	+
383	383	(((
384	384	To save battery life, N95S31B will establish a subscription before each uplink and close the subscription 3 seconds after uplink successful. Any downlink commands from server will only arrive during the subscription period.
385	385	)))
...	...	@@ -393,11 +393,14 @@
393	393
394	394	=== 2.2.8  Use TCP protocol to uplink data ===
395	395
	402	+
396	396	This feature is supported since firmware version v110
397	397
398	398	* (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/ Set to use TCP protocol to uplink
399	399	* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600   **(%%) ~/~/ to set TCP server address and port
400	400
	408	+
	409	+
401	401	[[image:1657352898400-901.png]]
402	402
403	403
...	...	@@ -407,6 +407,7 @@
407	407
408	408	=== 2.2.9  Change Update Interval ===
409	409
	419	+
410	410	User can use below command to change the (% style="color:green" %)**uplink interval**.
411	411
412	412	* (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
...	...	@@ -453,10 +453,10 @@
453	453
454	454	(% style="color:red" %)
455	455	1. (((
456		-All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]].
	466	+**All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]].**
457	457	)))
458	458	1. (((
459		-By default, the device will send an uplink message every 1 hour.
	469	+**By default, the device will send an uplink message every 1 hour.**
460	460
461	461
462	462
...	...	@@ -465,6 +465,7 @@
465	465
466	466	=== 2.3.1  Payload Analyze ===
467	467
	478	+
468	468	N95S31B uplink payload includes in total 21 bytes
469	469
470	470
...	...	@@ -499,6 +499,8 @@
499	499	)))
500	500
501	501	(((
	513	+
	514	+
502	502	(((
503	503	If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data.
504	504	)))
...	...	@@ -531,6 +531,7 @@
531	531
532	532	=== 2.3.2  Device ID ===
533	533
	547	+
534	534	(((
535	535	By default, the Device ID equal to the last 6 bytes of IMEI.
536	536	)))
...	...	@@ -555,6 +555,7 @@
555	555
556	556	=== 2.3.3  Version Info ===
557	557
	572	+
558	558	(((
559	559	These bytes include the hardware and software version.
560	560	)))
...	...	@@ -582,6 +582,7 @@
582	582
583	583	=== 2.3.4  Battery Info ===
584	584
	600	+
585	585	(((
586	586	Ex1: 0x0B45 = 2885mV
587	587	)))
...	...	@@ -594,6 +594,7 @@
594	594
595	595	=== 2.3.5  Signal Strength ===
596	596
	613	+
597	597	(((
598	598	NB-IoT Network signal Strength.
599	599	)))
...	...	@@ -626,6 +626,7 @@
626	626
627	627	=== 2.3.6  Temperature & Humidity ===
628	628
	646	+
629	629	The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server.
630	630
631	631	[[image:image-20220709161741-3.png]]
...	...	@@ -644,6 +644,7 @@
644	644
645	645	== 2.4  Downlink Payload ==
646	646
	665	+
647	647	By default, N95S31B prints the downlink payload to console port.
648	648
649	649	[[image:image-20220709100028-1.png]]
...	...	@@ -696,6 +696,7 @@
696	696
697	697	== 2.5  ​Battery Analysis ==
698	698
	718	+
699	699	=== 2.5.1  ​Battery Type ===
700	700
701	701
...	...	@@ -723,8 +723,9 @@
723	723
724	724	=== 2.5.2  Power consumption Analyze ===
725	725
	746	+
726	726	(((
727		-The file **DRAGINO_N95S31B-Power-Analyzer.pdf** from [[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/N95S31B/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/N95S31B/]] describes a detail measurement to analyze the power consumption in different case. User can use it for design guideline for their project.
	748	+The file **DRAGINO_N95S31B-Power-Analyzer.pdf** from [[https:~~/~~/www.dropbox.com/sh/mlpd6l05bogvaf6/AABwAJLMttqG7i~~-~~-AyZcQkoua?dl=0>>https://www.dropbox.com/sh/mlpd6l05bogvaf6/AABwAJLMttqG7i--AyZcQkoua?dl=0]] describes a detail measurement to analyze the power consumption in different case. User can use it for design guideline for their project.
728	728	)))
729	729
730	730	(((
...	...	@@ -734,6 +734,7 @@
734	734
735	735	=== 2.5.3  ​Battery Note ===
736	736
	758	+
737	737	(((
738	738	The Li-SICO battery is designed for small current / long period application. It is not good to use a high current, short period transmit method. The recommended minimum period for use of this battery is 5 minutes. If you use a shorter period time to uplink data, then the battery life may be decreased.
739	739	)))
...	...	@@ -756,6 +756,7 @@
756	756
757	757	= 3. ​ Access NB-IoT Module =
758	758
	781	+
759	759	(((
760	760	Users can directly access the AT command set of the NB-IoT module.
761	761	)))
...	...	@@ -762,6 +762,8 @@
762	762
763	763	(((
764	764	The AT Command set can refer the BC35-G NB-IoT Module AT Command: [[https:~~/~~/www.dragino.com/downloads/index.php?dir=datasheet/other_vendors/BC35-G/>>url:https://www.dragino.com/downloads/index.php?dir=datasheet/other_vendors/BC35-G/]]
	788	+
	789	+
765	765	)))
766	766
767	767	[[image:1657333200519-600.png]]
...	...	@@ -770,11 +770,13 @@
770	770
771	771	= 4.  Using the AT Commands =
772	772
	798	+
773	773	== 4.1  Access AT Commands ==
774	774
775		-See NBSN95 AT Command in this link for detail:  [[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN95/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN95/]]
776	776
	802	+See NBSN95 AT Command in this link for detail:  [[https:~~/~~/www.dropbox.com/sh/jao1xt9kw5r3yq4/AAAMpJkZzExF2JLbRWxGoQ9Na?dl=0>>https://www.dropbox.com/sh/jao1xt9kw5r3yq4/AAAMpJkZzExF2JLbRWxGoQ9Na?dl=0]]
777	777
	804	+
778	778	AT+<CMD>?  : Help on <CMD>
779	779
780	780	AT+<CMD>         : Run <CMD>
...	...	@@ -848,6 +848,7 @@
848	848
849	849	= ​5.  FAQ =
850	850
	878	+
851	851	== 5.1 ​ How to Upgrade Firmware ==
852	852
853	853
...	...	@@ -863,7 +863,7 @@
863	863
864	864
865	865	(((
866		-(% style="color:red" %)Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update.
	894	+(% style="color:red" %)**Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update.**
867	867	)))
868	868	)))
869	869
...	...	@@ -871,6 +871,7 @@
871	871
872	872	= 6.  Trouble Shooting =
873	873
	902	+
874	874	== 6.1  ​Connection problem when uploading firmware ==
875	875
876	876
...	...	@@ -886,6 +886,7 @@
886	886
887	887	== 6.2  AT Command input doesn't work ==
888	888
	918	+
889	889	(((
890	890	In the case if user can see the console output but can't type input to the device. Please check if you already include the (% style="color:green" %)**ENTER**(%%) while sending out the command. Some serial tool doesn't send (% style="color:green" %)**ENTER**(%%) while press the send key, user need to add ENTER in their string.
891	891
...	...	@@ -935,5 +935,9 @@
935	935
936	936	= 9.  Support =
937	937
	968	+
938	938	* Support is provided Monday to Friday, from 09:00 to 18:00 GMT+8. Due to different timezones we cannot offer live support. However, your questions will be answered as soon as possible in the before-mentioned schedule.
939	939	* Provide as much information as possible regarding your enquiry (product models, accurately describe your problem and steps to replicate it etc) and send a mail to [[support@dragino.com>>url:http://../../../../../../D:%5C%E5%B8%82%E5%9C%BA%E8%B5%84%E6%96%99%5C%E8%AF%B4%E6%98%8E%E4%B9%A6%5CLoRa%5CLT%E7%B3%BB%E5%88%97%5Csupport@dragino.com]]
	971	+
	972	+
	973	+