Summary

• Page properties (2 modified, 0 added, 0 removed)
• Attachments (0 modified, 2 added, 0 removed)
  • image-20220908154949-1.png
  • image-20220908163102-2.png

Details

Page properties

Author

...	...	@@ -1,1 +1,1 @@
1		-XWiki.Xiaoling
	1	+XWiki.David

Content

...	...	@@ -17,6 +17,7 @@
17	17
18	18	= 1.  Introduction =
19	19
	20	+
20	20	== 1.1 ​ What is N95S31B NB-IoT Sensor Node ==
21	21
22	22	(((
...	...	@@ -55,6 +55,7 @@
55	55
56	56	== 1.2 ​ Features ==
57	57
	59	+
58	58	* NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD
59	59	* Monitor Temperature & Humidity via SHT31
60	60	* AT Commands to change parameters
...	...	@@ -66,8 +66,6 @@
66	66	* Micro SIM card slot for NB-IoT SIM
67	67	* 8500mAh Battery for long term use
68	68
69		-
70		-
71	71	== 1.3  Specification ==
72	72
73	73
...	...	@@ -93,10 +93,9 @@
93	93	* Max continuously current: 130mA
94	94	* Max boost current: 2A, 1 second
95	95
96		-
97		-
98	98	== ​1.4  Applications ==
99	99
	98	+
100	100	* Smart Buildings & Home Automation
101	101	* Logistics and Supply Chain Management
102	102	* Smart Metering
...	...	@@ -108,15 +108,20 @@
108	108	​
109	109
110	110
	110	+
111	111	== 1.5  Pin Definitions & Switch ==
112	112
	113	+
113	113	N95S31B use the mother board from NBSN95 which as below.
114	114
	116	+
115	115	[[image:image-20220709144723-1.png]]
116	116
117	117
	120	+
118	118	=== 1.5.1 Jumper JP2 ===
119	119
	123	+
120	120	Power on Device when put this jumper.
121	121
122	122
...	...	@@ -123,6 +123,7 @@
123	123
124	124	=== 1.5.2 BOOT MODE / SW1 ===
125	125
	130	+
126	126	(((
127	127	1) ISP: upgrade mode, device won't have any signal in this mode. but ready for upgrade firmware. LED won't work. Firmware won't run.
128	128	)))
...	...	@@ -135,6 +135,7 @@
135	135
136	136	=== 1.5.3 Reset Button ===
137	137
	143	+
138	138	Press to reboot the device.
139	139
140	140
...	...	@@ -141,14 +141,15 @@
141	141
142	142	=== 1.5.4 LED ===
143	143
	150	+
144	144	It will flash:
145	145
146	146	1. When boot the device in flash mode
147	147	1. Send an uplink packet
148	148
149		-
150	150	= 2.  Use N95S31B to communicate with IoT Server =
151	151
	158	+
152	152	== 2.1  How it works ==
153	153
154	154
...	...	@@ -181,6 +181,7 @@
181	181	[[image:image-20220709150546-2.png]]
182	182
183	183
	191	+
184	184	=== 2.2.1 Test Requirement ===
185	185
186	186
...	...	@@ -233,6 +233,7 @@
233	233
234	234	=== 2.2.3  Insert SIM card ===
235	235
	244	+
236	236	(((
237	237	Insert the NB-IoT Card get from your provider.
238	238	)))
...	...	@@ -248,14 +248,18 @@
248	248
249	249	=== 2.2.4  Connect USB – TTL to N95S31B to configure it ===
250	250
	260	+
251	251	(((
252	252	(((
253	253	User need to configure N95S31B via serial port to set the (% style="color:blue" %)**Server Address** / **Uplink Topic** (%%)to define where and how-to uplink packets. N95S31B support AT Commands, user can use a USB to TTL adapter to connect to N95S31B and use AT Commands to configure it, as below.
	264	+
	265	+
254	254	)))
255	255	)))
256	256
257	257	[[image:1657351312545-300.png]]
258	258
	271	+
259	259	**Connection:**
260	260
261	261	(% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND
...	...	@@ -279,8 +279,9 @@
279	279
280	280	[[image:1657329814315-101.png]]
281	281
	295	+
282	282	(((
283		-(% style="color:red" %)Note: the valid AT Commands can be found at:  (%%)[[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/N95S31B/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/N95S31B/]]
	297	+(% style="color:red" %)**Note: the valid AT Commands can be found at:  **(%%)**[[https:~~/~~/www.dropbox.com/sh/mlpd6l05bogvaf6/AABwAJLMttqG7i~~-~~-AyZcQkoua?dl=0>>https://www.dropbox.com/sh/mlpd6l05bogvaf6/AABwAJLMttqG7i--AyZcQkoua?dl=0]]**
284	284	)))
285	285
286	286
...	...	@@ -287,9 +287,10 @@
287	287
288	288	=== 2.2.5  Use CoAP protocol to uplink data ===
289	289
290		-(% style="color:red" %)Note: if you don't have CoAP server, you can refer this link to set up one: (%%)[[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/>>http://wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/]]
291	291
	305	+(% style="color:red" %)**Note: if you don't have CoAP server, you can refer this link to set up one: **(%%)**[[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/>>http://wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/]]**
292	292
	307	+
293	293	(((
294	294	**Use below commands:**
295	295	)))
...	...	@@ -337,6 +337,7 @@
337	337
338	338	=== 2.2.7  Use MQTT protocol to uplink data ===
339	339
	355	+
340	340	N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption.
341	341
342	342	* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
...	...	@@ -352,6 +352,7 @@
352	352
353	353	[[image:1657352645687-385.png]]
354	354
	371	+
355	355	(((
356	356	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.
357	357	)))
...	...	@@ -365,6 +365,7 @@
365	365
366	366	=== 2.2.8  Use TCP protocol to uplink data ===
367	367
	385	+
368	368	This feature is supported since firmware version v110
369	369
370	370	* (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/ Set to use TCP protocol to uplink
...	...	@@ -379,6 +379,7 @@
379	379
380	380	=== 2.2.9  Change Update Interval ===
381	381
	400	+
382	382	User can use below command to change the (% style="color:green" %)**uplink interval**.
383	383
384	384	* (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
...	...	@@ -387,13 +387,16 @@
387	387
388	388	)))
389	389
	409	+(% style="color:red" %)**NOTE:When the firmware version is v1.2 and later firmware:**
390	390
	411	+**By default, the device will send an uplink message every 2 hours. Each Uplink Include 8 set of records in this 2 hour (15 minute interval / record).**
391	391
	413	+
392	392	== 2.3  Uplink Payload ==
393	393
394	394
395	395	(((
396		-NBSN95 has different working mode for the connections of different type of sensors. This section describes these modes. User can use the AT Command (% style="color:blue" %)**AT+MOD**(%%) to set NBSN95 to different working modes.
	418	+N95S31B has different working mode for the connections of different type of sensors. This section describes these modes. User can use the AT Command (% style="color:blue" %)**AT+MOD**(%%) to set NBSN95 to different working modes.
397	397	)))
398	398
399	399
...	...	@@ -402,7 +402,7 @@
402	402	)))
403	403
404	404	(((
405		- (% style="color:blue" %)**AT+CFGMOD=2 ** (%%)~/~/will set the NBSN95 to work in MOD=2 distance mode which target to measure distance via Ultrasonic Sensor.
	427	+ (% style="color:blue" %)**AT+CFGMOD=2 ** (%%)~/~/will set the N95S31B to work in MOD=2 distance mode which target to measure distance via Ultrasonic Sensor.
406	406	)))
407	407
408	408
...	...	@@ -425,14 +425,19 @@
425	425
426	426	(% style="color:red" %)
427	427	1. (((
428		-All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]].
	450	+**All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]].**
429	429	)))
430	430	1. (((
431		-By default, the device will send an uplink message every 1 hour.
	453	+**By default, the device will send an uplink message every 1 hour.**
	454	+
	455	+
	456	+
	457	+
432	432	)))
433	433
434	434	=== 2.3.1  Payload Analyze ===
435	435
	462	+
436	436	N95S31B uplink payload includes in total 21 bytes
437	437
438	438
...	...	@@ -467,6 +467,8 @@
467	467	)))
468	468
469	469	(((
	497	+
	498	+
470	470	(((
471	471	If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data.
472	472	)))
...	...	@@ -493,12 +493,41 @@
493	493	)))
494	494
495	495	(((
496		-
	525	+(% style="color:red" %)**NOTE:When the firmware version is v1.2 and later firmware:**
497	497	)))
498	498
	528	+In this mode, uplink payload includes 91 bytes in total by default.
499	499
	530	+Each time the device uploads a data package, 8 sets of recorded data will be attached. Up to 32 sets of recorded data can be uploaded.
	531	+
	532	+|**Size(bytes)**|**8**|2|2|1|1|2|1|2|2|2|4|2|2|4
	533	+|**Value**|Device ID|Ver|BAT|Signal Strength|MOD|TemDS18B20|Interrupt|ADC|SHTTEM|SHTHUM|Time stamp |SHTTEM|SHTHUM|Time stamp .....
	534	+
	535	+If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the N95S31B uplink data.
	536	+
	537	+[[image:image-20220908154949-1.png]]
	538	+
	539	+The payload is ASCII string, representative same HEX:
	540	+
	541	+0x(% style="color:red" %)f868411056758782(% style="color:blue" %)000c(% style="color:green" %)0d0f(% style="color:red" %)0c(% style="color:blue" %)01(% style="color:green" %)0000(% style="color:red" %)00**//0030//**(% style="color:blue" %)**//0114//**(% style="color:red" %)**//0231//**(% style="color:green" %)**//63199d3c//**0113023163199d12//**0113023163199c5e**//0112023763199baa//**0112023263199af6**//0111023b631999a7//**0112023b631998f3**//011202426319983f//**01110242631996eb**//(%%) where:
	542	+
	543	+* (% style="color:red" %) Device ID: f868411056758782 = f868411056758782
	544	+* (% style="color:blue" %) Version: 0x000c=120=1.2
	545	+* (% style="color:green" %) BAT: 0x0d0f = 3343 mV = 3.343V
	546	+* (% style="color:red" %) Singal: 0x0c = 12
	547	+* (% style="color:blue" %) Mod: 0x01 = 1
	548	+* TemDS18B20: 0x0000= 0 = 0
	549	+* (% style="color:green" %)Interrupt: 0x00= 0
	550	+* (% style="color:green" %)adc: 0x0030= 48
	551	+* SHTTEM: 0x0114= 276 = 27.6
	552	+* SHTHUM:0x0231 =561=56.1%
	553	+* (% style="color:red" %) Time stamp : 0x6315537b =1662342011  ([[Unix Epoch Time>>url:http://www.epochconverter.com/]])
	554	+* (% style="color:red" %)SHTTEM,SHTHUM,Time stamp : 0113023163199d12
	555	+* 8 sets of recorded data: SHTTEM,SHTHUM,Time stamp : //**0113023163199c5e**//,.......
	556	+
500	500	=== 2.3.2  Device ID ===
501	501
	559	+
502	502	(((
503	503	By default, the Device ID equal to the last 6 bytes of IMEI.
504	504	)))
...	...	@@ -517,12 +517,25 @@
517	517
518	518	(((
519	519	The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID.
	578	+
	579	+
520	520	)))
521	521
	582	+(% style="color:red" %)**NOTE:When the firmware version is v1.2 and later firmware:**
522	522
523	523
	585	+By default, the Device ID equal to the last 15 bits of IMEI.
	586	+
	587	+User can use **AT+DEUI** to set Device ID
	588	+
	589	+**Example:**
	590	+
	591	+AT+DEUI=868411056754138
	592	+
	593	+
524	524	=== 2.3.3  Version Info ===
525	525
	596	+
526	526	(((
527	527	These bytes include the hardware and software version.
528	528	)))
...	...	@@ -550,6 +550,7 @@
550	550
551	551	=== 2.3.4  Battery Info ===
552	552
	624	+
553	553	(((
554	554	Ex1: 0x0B45 = 2885mV
555	555	)))
...	...	@@ -562,6 +562,7 @@
562	562
563	563	=== 2.3.5  Signal Strength ===
564	564
	637	+
565	565	(((
566	566	NB-IoT Network signal Strength.
567	567	)))
...	...	@@ -594,6 +594,7 @@
594	594
595	595	=== 2.3.6  Temperature & Humidity ===
596	596
	670	+
597	597	The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server.
598	598
599	599	[[image:image-20220709161741-3.png]]
...	...	@@ -612,8 +612,9 @@
612	612
613	613	== 2.4  Downlink Payload ==
614	614
615		-By default, NDDS75 prints the downlink payload to console port.
616	616
	690	+By default, N95S31B prints the downlink payload to console port.
	691	+
617	617	[[image:image-20220709100028-1.png]]
618	618
619	619
...	...	@@ -650,7 +650,7 @@
650	650	)))
651	651
652	652	(((
653		-If payload = 0x04FF, it will reset the NDDS75
	728	+If payload = 0x04FF, it will reset the N95S31B
654	654	)))
655	655
656	656
...	...	@@ -661,12 +661,59 @@
661	661	)))
662	662
663	663
	739	+== 2.5 Humidity and Temperature alarm function ==
664	664
665		-== 2.5  ​Battery Analysis ==
	741	+➢ AT Command:
666	666
667		-=== 2.5.1  ​Battery Type ===
	743	+AT+ SHHUM=min,max
668	668
	745	+² When min=0, and max≠0, Alarm higher than max
669	669
	747	+² When min≠0, and max=0, Alarm lower than min
	748	+
	749	+² When min≠0 and max≠0, Alarm higher than max or lower than min
	750	+
	751	+Example:
	752	+
	753	+AT+ SHHUM=50,80 ~/~/ Alarm when humidity lower than 50.
	754	+
	755	+
	756	+AT+ SHTEMP=min,max
	757	+
	758	+² When min=0, and max≠0, Alarm higher than max
	759	+
	760	+² When min≠0, and max=0, Alarm lower than min
	761	+
	762	+² When min≠0 and max≠0, Alarm higher than max or lower than min
	763	+
	764	+Example:
	765	+
	766	+AT+ SHTEMP=20,30 ~/~/ Alarm when temperature lower than 20.
	767	+
	768	+== 2.6 Set the number of data to be uploaded and the recording time ==
	769	+
	770	+➢ AT Command:
	771	+
	772	+AT+TR=900  ~/~/The unit is seconds, and the default is to record data once every 900 seconds.( The minimum can be set to 180 seconds)
	773	+
	774	+AT+NOUD=8  ~/~/The device uploads 8 sets of recorded data by default. Up to 32 sets of record data can be uploaded.
	775	+
	776	+== 2.7 Read or Clear cached data ==
	777	+
	778	+➢ AT Command:
	779	+
	780	+AT+CDP ~/~/ Read cached data
	781	+
	782	+[[image:image-20220908163102-2.png]]
	783	+
	784	+AT+CDP=0 ~/~/ Clear cached data
	785	+
	786	+== 2.8  ​Battery Analysis ==
	787	+
	788	+
	789	+=== 2.8.1  ​Battery Type ===
	790	+
	791	+
670	670	(((
671	671	The N95S31B battery is a combination of an 8500mAh Li/SOCI2 Battery and a Super Capacitor. The battery is none-rechargeable battery type with a low discharge rate (<2% per year). This type of battery is commonly used in IoT devices such as water meter.
672	672	)))
...	...	@@ -689,10 +689,11 @@
689	689
690	690
691	691
692		-=== 2.5.2  Power consumption Analyze ===
	814	+=== 2.8.2  Power consumption Analyze ===
693	693
	816	+
694	694	(((
695		-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.
	818	+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.
696	696	)))
697	697
698	698	(((
...	...	@@ -700,8 +700,9 @@
700	700	)))
701	701
702	702
703		-=== 2.5.3  ​Battery Note ===
	826	+=== 2.8.3  ​Battery Note ===
704	704
	828	+
705	705	(((
706	706	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.
707	707	)))
...	...	@@ -708,7 +708,7 @@
708	708
709	709
710	710
711		-=== 2.5.4  Replace the battery ===
	835	+=== 2.8.4  Replace the battery ===
712	712
713	713
714	714	(((
...	...	@@ -724,6 +724,7 @@
724	724
725	725	= 3. ​ Access NB-IoT Module =
726	726
	851	+
727	727	(((
728	728	Users can directly access the AT command set of the NB-IoT module.
729	729	)))
...	...	@@ -730,6 +730,8 @@
730	730
731	731	(((
732	732	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/]]
	858	+
	859	+
733	733	)))
734	734
735	735	[[image:1657333200519-600.png]]
...	...	@@ -738,11 +738,13 @@
738	738
739	739	= 4.  Using the AT Commands =
740	740
	868	+
741	741	== 4.1  Access AT Commands ==
742	742
743		-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/]]
744	744
	872	+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]]
745	745
	874	+
746	746	AT+<CMD>?  : Help on <CMD>
747	747
748	748	AT+<CMD>         : Run <CMD>
...	...	@@ -782,7 +782,24 @@
782	782
783	783	AT+SERVADDR  : Server Address
784	784
	914	+AT+TR      : Get or Set record time
785	785
	916	+AT+APN     : Get or set the APN
	917	+
	918	+AT+FBAND   : Get or Set whether to automatically modify the frequency band
	919	+
	920	+AT+DNSCFG  : Get or Set DNS Server
	921	+
	922	+AT+GETSENSORVALUE   : Returns the current sensor measurement
	923	+
	924	+AT+NOUD      : Get or Set the number of data to be uploaded
	925	+
	926	+AT+CDP     : Read or Clear cached data
	927	+
	928	+AT+SHTEMP: Get or Set alarm of temp
	929	+
	930	+AT+SHHUM: Get or Set alarm of moisture
	931	+
786	786	(% style="color:#037691" %)**COAP Management**
787	787
788	788	AT+URI            : Resource parameters
...	...	@@ -816,6 +816,7 @@
816	816
817	817	= ​5.  FAQ =
818	818
	965	+
819	819	== 5.1 ​ How to Upgrade Firmware ==
820	820
821	821
...	...	@@ -831,7 +831,7 @@
831	831
832	832
833	833	(((
834		-(% style="color:red" %)Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update.
	981	+(% style="color:red" %)**Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update.**
835	835	)))
836	836	)))
837	837
...	...	@@ -839,6 +839,7 @@
839	839
840	840	= 6.  Trouble Shooting =
841	841
	989	+
842	842	== 6.1  ​Connection problem when uploading firmware ==
843	843
844	844
...	...	@@ -854,6 +854,7 @@
854	854
855	855	== 6.2  AT Command input doesn't work ==
856	856
	1005	+
857	857	(((
858	858	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.
859	859
...	...	@@ -903,5 +903,8 @@
903	903
904	904	= 9.  Support =
905	905
	1055	+
906	906	* 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.
907	907	* 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]]
	1058	+
	1059	+

image-20220908154949-1.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.David

Size

...	...	@@ -1,0 +1,1 @@
	1	+58.5 KB

Content

image-20220908163102-2.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.David

Size

...	...	@@ -1,0 +1,1 @@
	1	+29.7 KB

Content