Summary

• Page properties (1 modified, 0 added, 0 removed)
• Attachments (0 modified, 1 added, 0 removed)
  • 1657520100595-569.png

Details

Page properties

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
...	...	@@ -78,6 +78,7 @@
78	78	* Operating Temperature: -40 ~~ 85°C
79	79
80	80
	83	+
81	81	(% style="color:#037691" %)**NB-IoT Spec:**
82	82
83	83	* - B1 @H-FDD: 2100MHz
...	...	@@ -88,6 +88,7 @@
88	88	* - B28 @H-FDD: 700MHz
89	89
90	90
	94	+
91	91	(% style="color:#037691" %)**Battery:**
92	92
93	93	* Li/SOCI2 un-chargeable battery
...	...	@@ -101,6 +101,7 @@
101	101
102	102	== ​1.4  Applications ==
103	103
	108	+
104	104	* Smart Buildings & Home Automation
105	105	* Logistics and Supply Chain Management
106	106	* Smart Metering
...	...	@@ -112,15 +112,20 @@
112	112	​
113	113
114	114
115		-== 1.5  Pin Definitions ==
116	116
	121	+== 1.5  Pin Definitions & Switch ==
	122	+
	123	+
117	117	N95S31B use the mother board from NBSN95 which as below.
118	118
	126	+
119	119	[[image:image-20220709144723-1.png]]
120	120
121	121
	130	+
122	122	=== 1.5.1 Jumper JP2 ===
123	123
	133	+
124	124	Power on Device when put this jumper.
125	125
126	126
...	...	@@ -127,6 +127,7 @@
127	127
128	128	=== 1.5.2 BOOT MODE / SW1 ===
129	129
	140	+
130	130	(((
131	131	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.
132	132	)))
...	...	@@ -139,6 +139,7 @@
139	139
140	140	=== 1.5.3 Reset Button ===
141	141
	153	+
142	142	Press to reboot the device.
143	143
144	144
...	...	@@ -145,6 +145,7 @@
145	145
146	146	=== 1.5.4 LED ===
147	147
	160	+
148	148	It will flash:
149	149
150	150	1. When boot the device in flash mode
...	...	@@ -155,6 +155,7 @@
155	155
156	156	= 2.  Use N95S31B to communicate with IoT Server =
157	157
	171	+
158	158	== 2.1  How it works ==
159	159
160	160
...	...	@@ -171,7 +171,7 @@
171	171
172	172	)))
173	173
174		-[[image:1657350248151-650.png]]
	188	+[[image:1657520100595-569.png]]
175	175
176	176	(((
177	177
...	...	@@ -187,26 +187,49 @@
187	187	[[image:image-20220709150546-2.png]]
188	188
189	189
	204	+
190	190	=== 2.2.1 Test Requirement ===
191	191
192	192
	208	+(((
193	193	To use N95S31B in your city, make sure meet below requirements:
	210	+)))
194	194
195		-* Your local operator has already distributed a NB-IoT Network there.
196		-* The local NB-IoT network used the band that N95S31B supports.
197		-* Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
	212	+* (((
	213	+Your local operator has already distributed a NB-IoT Network there.
	214	+)))
	215	+* (((
	216	+The local NB-IoT network used the band that N95S31B supports.
	217	+)))
	218	+* (((
	219	+Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
	220	+)))
198	198
	222	+(((
199	199	Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8.
	224	+)))
200	200
	226	+(((
201	201	N95S31B supports different communication protocol such as :
	228	+)))
202	202
203	203	(((
204		-* CoAP  ((% style="color:red" %)120.24.4.116:5683(%%))
205		-* raw UDP  ((% style="color:red" %)120.24.4.116:5601(%%))
206		-* MQTT  ((% style="color:red" %)120.24.4.116:1883(%%))
207		-* TCP  ((% style="color:red" %)120.24.4.116:5600(%%))
	231	+* (((
	232	+CoAP  ((% style="color:red" %)120.24.4.116:5683(%%))
	233	+)))
	234	+* (((
	235	+raw UDP  ((% style="color:red" %)120.24.4.116:5601(%%))
	236	+)))
	237	+* (((
	238	+MQTT  ((% style="color:red" %)120.24.4.116:1883(%%))
	239	+)))
	240	+* (((
	241	+TCP  ((% style="color:red" %)120.24.4.116:5600(%%))
	242	+)))
208	208
	244	+(((
209	209	We will show how to use with each protocol. The IP addresses above are our test server. User need to change to point their corresponding server.
	246	+)))
210	210
211	211
212	212	)))
...	...	@@ -217,6 +217,7 @@
217	217
218	218	=== 2.2.3  Insert SIM card ===
219	219
	257	+
220	220	(((
221	221	Insert the NB-IoT Card get from your provider.
222	222	)))
...	...	@@ -232,14 +232,18 @@
232	232
233	233	=== 2.2.4  Connect USB – TTL to N95S31B to configure it ===
234	234
	273	+
235	235	(((
236	236	(((
237	237	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.
	277	+
	278	+
238	238	)))
239	239	)))
240	240
241	241	[[image:1657351312545-300.png]]
242	242
	284	+
243	243	**Connection:**
244	244
245	245	(% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND
...	...	@@ -263,8 +263,9 @@
263	263
264	264	[[image:1657329814315-101.png]]
265	265
	308	+
266	266	(((
267		-(% 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/]]
	310	+(% 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]]**
268	268	)))
269	269
270	270
...	...	@@ -271,9 +271,10 @@
271	271
272	272	=== 2.2.5  Use CoAP protocol to uplink data ===
273	273
274		-(% 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/]]
275	275
	318	+(% 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/]]**
276	276
	320	+
277	277	(((
278	278	**Use below commands:**
279	279	)))
...	...	@@ -312,6 +312,8 @@
312	312	* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/ to set UDP server address and port
313	313	* (% style="color:blue" %)**AT+CFM=1       ** (%%) ~/~/ If the server does not respond, this command is unnecessary
314	314
	359	+
	360	+
315	315	[[image:1657352391268-297.png]]
316	316
317	317
...	...	@@ -321,6 +321,7 @@
321	321
322	322	=== 2.2.7  Use MQTT protocol to uplink data ===
323	323
	370	+
324	324	N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption.
325	325
326	326	* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
...	...	@@ -331,11 +331,14 @@
331	331	* (% style="color:blue" %)**AT+PUBTOPIC=f9527                               **(%%)~/~/Set the sending topic of MQTT
332	332	* (% style="color:blue" %)**AT+SUBTOPIC=Ns9527          **(%%) ~/~/Set the subscription topic of MQTT
333	333
	381	+
	382	+
334	334	[[image:1657352634421-276.png]]
335	335
336	336
337	337	[[image:1657352645687-385.png]]
338	338
	388	+
339	339	(((
340	340	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.
341	341	)))
...	...	@@ -349,11 +349,14 @@
349	349
350	350	=== 2.2.8  Use TCP protocol to uplink data ===
351	351
	402	+
352	352	This feature is supported since firmware version v110
353	353
354	354	* (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/ Set to use TCP protocol to uplink
355	355	* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600   **(%%) ~/~/ to set TCP server address and port
356	356
	408	+
	409	+
357	357	[[image:1657352898400-901.png]]
358	358
359	359
...	...	@@ -363,6 +363,7 @@
363	363
364	364	=== 2.2.9  Change Update Interval ===
365	365
	419	+
366	366	User can use below command to change the (% style="color:green" %)**uplink interval**.
367	367
368	368	* (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
...	...	@@ -376,30 +376,52 @@
376	376	== 2.3  Uplink Payload ==
377	377
378	378
379		-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.
	433	+(((
	434	+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.
	435	+)))
380	380
381	381
	438	+(((
382	382	For example:
	440	+)))
383	383
384		- (% 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.
	442	+(((
	443	+ (% 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.
	444	+)))
385	385
386	386
	447	+(((
387	387	The uplink payloads are composed in  ASCII String. For example:
	449	+)))
388	388
	451	+(((
389	389	0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload:
	453	+)))
390	390
	455	+(((
391	391	0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes
	457	+)))
392	392
393	393
	460	+(((
394	394	(% style="color:red" %)**NOTE:**
	462	+)))
395	395
396	396	(% style="color:red" %)
397		-1. All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]].
398		-1. By default, the device will send an uplink message every 1 hour.
	465	+1. (((
	466	+**All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]].**
	467	+)))
	468	+1. (((
	469	+**By default, the device will send an uplink message every 1 hour.**
399	399
400	400
	472	+
	473	+
	474	+)))
	475	+
401	401	=== 2.3.1  Payload Analyze ===
402	402
	478	+
403	403	N95S31B uplink payload includes in total 21 bytes
404	404
405	405
...	...	@@ -434,6 +434,8 @@
434	434	)))
435	435
436	436	(((
	513	+
	514	+
437	437	(((
438	438	If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data.
439	439	)))
...	...	@@ -466,6 +466,7 @@
466	466
467	467	=== 2.3.2  Device ID ===
468	468
	547	+
469	469	(((
470	470	By default, the Device ID equal to the last 6 bytes of IMEI.
471	471	)))
...	...	@@ -491,14 +491,25 @@
491	491	=== 2.3.3  Version Info ===
492	492
493	493
	573	+(((
494	494	These bytes include the hardware and software version.
	575	+)))
495	495
	577	+(((
496	496	Higher byte: Specify hardware version: always 0x00 for N95S31B
	579	+)))
497	497
	581	+(((
498	498	Lower byte: Specify the software version: 0x6E=110, means firmware version 110
	583	+)))
499	499
	585	+(((
	586	+
	587	+)))
500	500
	589	+(((
501	501	For example: 0x00 6E: this device is N95S31B with firmware version 110.
	591	+)))
502	502
503	503	(((
504	504
...	...	@@ -507,6 +507,7 @@
507	507
508	508	=== 2.3.4  Battery Info ===
509	509
	600	+
510	510	(((
511	511	Ex1: 0x0B45 = 2885mV
512	512	)))
...	...	@@ -519,6 +519,7 @@
519	519
520	520	=== 2.3.5  Signal Strength ===
521	521
	613	+
522	522	(((
523	523	NB-IoT Network signal Strength.
524	524	)))
...	...	@@ -551,6 +551,7 @@
551	551
552	552	=== 2.3.6  Temperature & Humidity ===
553	553
	646	+
554	554	The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server.
555	555
556	556	[[image:image-20220709161741-3.png]]
...	...	@@ -569,8 +569,9 @@
569	569
570	570	== 2.4  Downlink Payload ==
571	571
572		-By default, NDDS75 prints the downlink payload to console port.
573	573
	666	+By default, N95S31B prints the downlink payload to console port.
	667	+
574	574	[[image:image-20220709100028-1.png]]
575	575
576	576
...	...	@@ -607,7 +607,7 @@
607	607	)))
608	608
609	609	(((
610		-If payload = 0x04FF, it will reset the NDDS75
	704	+If payload = 0x04FF, it will reset the N95S31B
611	611	)))
612	612
613	613
...	...	@@ -621,6 +621,7 @@
621	621
622	622	== 2.5  ​Battery Analysis ==
623	623
	718	+
624	624	=== 2.5.1  ​Battery Type ===
625	625
626	626
...	...	@@ -648,8 +648,9 @@
648	648
649	649	=== 2.5.2  Power consumption Analyze ===
650	650
	746	+
651	651	(((
652		-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.
653	653	)))
654	654
655	655	(((
...	...	@@ -659,6 +659,7 @@
659	659
660	660	=== 2.5.3  ​Battery Note ===
661	661
	758	+
662	662	(((
663	663	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.
664	664	)))
...	...	@@ -681,6 +681,7 @@
681	681
682	682	= 3. ​ Access NB-IoT Module =
683	683
	781	+
684	684	(((
685	685	Users can directly access the AT command set of the NB-IoT module.
686	686	)))
...	...	@@ -687,6 +687,8 @@
687	687
688	688	(((
689	689	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	+
690	690	)))
691	691
692	692	[[image:1657333200519-600.png]]
...	...	@@ -695,11 +695,13 @@
695	695
696	696	= 4.  Using the AT Commands =
697	697
	798	+
698	698	== 4.1  Access AT Commands ==
699	699
700		-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/]]
701	701
	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]]
702	702
	804	+
703	703	AT+<CMD>?  : Help on <CMD>
704	704
705	705	AT+<CMD>         : Run <CMD>
...	...	@@ -773,6 +773,7 @@
773	773
774	774	= ​5.  FAQ =
775	775
	878	+
776	776	== 5.1 ​ How to Upgrade Firmware ==
777	777
778	778
...	...	@@ -787,13 +787,16 @@
787	787	(((
788	788
789	789
790		-(% style="color:red" %)Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update.
	893	+(((
	894	+(% style="color:red" %)**Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update.**
791	791	)))
	896	+)))
792	792
793	793
794	794
795	795	= 6.  Trouble Shooting =
796	796
	902	+
797	797	== 6.1  ​Connection problem when uploading firmware ==
798	798
799	799
...	...	@@ -809,6 +809,7 @@
809	809
810	810	== 6.2  AT Command input doesn't work ==
811	811
	918	+
812	812	(((
813	813	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.
814	814
...	...	@@ -858,5 +858,9 @@
858	858
859	859	= 9.  Support =
860	860
	968	+
861	861	* 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.
862	862	* 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	+

1657520100595-569.png

Author

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

Size

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

Content