Summary

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

Details

Page properties

Content

...	...	@@ -356,8 +356,6 @@
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		-
361	361	[[image:1657352391268-297.png]]
362	362
363	363
...	...	@@ -367,7 +367,6 @@
367	367
368	368	=== 2.2.7  Use MQTT protocol to uplink data ===
369	369
370		-
371	371	N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption.
372	372
373	373	* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
...	...	@@ -378,14 +378,11 @@
378	378	* (% style="color:blue" %)**AT+PUBTOPIC=f9527                               **(%%)~/~/Set the sending topic of MQTT
379	379	* (% style="color:blue" %)**AT+SUBTOPIC=Ns9527          **(%%) ~/~/Set the subscription topic of MQTT
380	380
381		-
382		-
383	383	[[image:1657352634421-276.png]]
384	384
385	385
386	386	[[image:1657352645687-385.png]]
387	387
388		-
389	389	(((
390	390	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.
391	391	)))
...	...	@@ -399,14 +399,11 @@
399	399
400	400	=== 2.2.8  Use TCP protocol to uplink data ===
401	401
402		-
403	403	This feature is supported since firmware version v110
404	404
405	405	* (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/ Set to use TCP protocol to uplink
406	406	* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600   **(%%) ~/~/ to set TCP server address and port
407	407
408		-
409		-
410	410	[[image:1657352898400-901.png]]
411	411
412	412
...	...	@@ -416,7 +416,6 @@
416	416
417	417	=== 2.2.9  Change Update Interval ===
418	418
419		-
420	420	User can use below command to change the (% style="color:green" %)**uplink interval**.
421	421
422	422	* (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
...	...	@@ -463,10 +463,10 @@
463	463
464	464	(% style="color:red" %)
465	465	1. (((
466		-**All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]].**
	456	+All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]].
467	467	)))
468	468	1. (((
469		-**By default, the device will send an uplink message every 1 hour.**
	459	+By default, the device will send an uplink message every 1 hour.
470	470
471	471
472	472
...	...	@@ -475,7 +475,6 @@
475	475
476	476	=== 2.3.1  Payload Analyze ===
477	477
478		-
479	479	N95S31B uplink payload includes in total 21 bytes
480	480
481	481
...	...	@@ -510,8 +510,6 @@
510	510	)))
511	511
512	512	(((
513		-
514		-
515	515	(((
516	516	If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data.
517	517	)))
...	...	@@ -544,7 +544,6 @@
544	544
545	545	=== 2.3.2  Device ID ===
546	546
547		-
548	548	(((
549	549	By default, the Device ID equal to the last 6 bytes of IMEI.
550	550	)))
...	...	@@ -569,7 +569,6 @@
569	569
570	570	=== 2.3.3  Version Info ===
571	571
572		-
573	573	(((
574	574	These bytes include the hardware and software version.
575	575	)))
...	...	@@ -597,7 +597,6 @@
597	597
598	598	=== 2.3.4  Battery Info ===
599	599
600		-
601	601	(((
602	602	Ex1: 0x0B45 = 2885mV
603	603	)))
...	...	@@ -610,7 +610,6 @@
610	610
611	611	=== 2.3.5  Signal Strength ===
612	612
613		-
614	614	(((
615	615	NB-IoT Network signal Strength.
616	616	)))
...	...	@@ -643,7 +643,6 @@
643	643
644	644	=== 2.3.6  Temperature & Humidity ===
645	645
646		-
647	647	The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server.
648	648
649	649	[[image:image-20220709161741-3.png]]
...	...	@@ -662,7 +662,6 @@
662	662
663	663	== 2.4  Downlink Payload ==
664	664
665		-
666	666	By default, N95S31B prints the downlink payload to console port.
667	667
668	668	[[image:image-20220709100028-1.png]]
...	...	@@ -715,7 +715,6 @@
715	715
716	716	== 2.5  ​Battery Analysis ==
717	717
718		-
719	719	=== 2.5.1  ​Battery Type ===
720	720
721	721
...	...	@@ -743,9 +743,8 @@
743	743
744	744	=== 2.5.2  Power consumption Analyze ===
745	745
746		-
747	747	(((
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.
	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.
749	749	)))
750	750
751	751	(((
...	...	@@ -755,7 +755,6 @@
755	755
756	756	=== 2.5.3  ​Battery Note ===
757	757
758		-
759	759	(((
760	760	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.
761	761	)))
...	...	@@ -778,7 +778,6 @@
778	778
779	779	= 3. ​ Access NB-IoT Module =
780	780
781		-
782	782	(((
783	783	Users can directly access the AT command set of the NB-IoT module.
784	784	)))
...	...	@@ -785,8 +785,6 @@
785	785
786	786	(((
787	787	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		-
790	790	)))
791	791
792	792	[[image:1657333200519-600.png]]
...	...	@@ -795,13 +795,11 @@
795	795
796	796	= 4.  Using the AT Commands =
797	797
798		-
799	799	== 4.1  Access AT Commands ==
800	800
	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/]]
801	801
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]]
803	803
804		-
805	805	AT+<CMD>?  : Help on <CMD>
806	806
807	807	AT+<CMD>         : Run <CMD>
...	...	@@ -875,7 +875,6 @@
875	875
876	876	= ​5.  FAQ =
877	877
878		-
879	879	== 5.1 ​ How to Upgrade Firmware ==
880	880
881	881
...	...	@@ -891,7 +891,7 @@
891	891
892	892
893	893	(((
894		-(% style="color:red" %)**Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update.**
	866	+(% style="color:red" %)Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update.
895	895	)))
896	896	)))
897	897
...	...	@@ -899,7 +899,6 @@
899	899
900	900	= 6.  Trouble Shooting =
901	901
902		-
903	903	== 6.1  ​Connection problem when uploading firmware ==
904	904
905	905
...	...	@@ -915,7 +915,6 @@
915	915
916	916	== 6.2  AT Command input doesn't work ==
917	917
918		-
919	919	(((
920	920	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.
921	921
...	...	@@ -965,9 +965,5 @@
965	965
966	966	= 9.  Support =
967	967
968		-
969	969	* 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.
970	970	* 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		-