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
...	...	@@ -77,6 +77,8 @@
77	77	* Supply Voltage: 2.1v ~~ 3.6v
78	78	* Operating Temperature: -40 ~~ 85°C
79	79
	82	+
	83	+
80	80	(% style="color:#037691" %)**NB-IoT Spec:**
81	81
82	82	* - B1 @H-FDD: 2100MHz
...	...	@@ -86,9 +86,10 @@
86	86	* - B20 @H-FDD: 800MHz
87	87	* - B28 @H-FDD: 700MHz
88	88
89		-(% style="color:#037691" %)**Battery:**
90	90
91	91
	95	+(% style="color:#037691" %)**Battery:**
	96	+
92	92	* Li/SOCI2 un-chargeable battery
93	93	* Capacity: 8500mAh
94	94	* Self Discharge: <1% / Year @ 25°C
...	...	@@ -95,8 +95,12 @@
95	95	* Max continuously current: 130mA
96	96	* Max boost current: 2A, 1 second
97	97
	103	+
	104	+
	105	+
98	98	== ​1.4  Applications ==
99	99
	108	+
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
111		-== 1.5  Pin Definitions ==
112	112
	121	+== 1.5  Pin Definitions & Switch ==
	122	+
	123	+
113	113	N95S31B use the mother board from NBSN95 which as below.
114	114
	126	+
115	115	[[image:image-20220709144723-1.png]]
116	116
117	117
	130	+
118	118	=== 1.5.1 Jumper JP2 ===
119	119
	133	+
120	120	Power on Device when put this jumper.
121	121
122	122
...	...	@@ -123,14 +123,20 @@
123	123
124	124	=== 1.5.2 BOOT MODE / SW1 ===
125	125
	140	+
	141	+(((
126	126	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.
	143	+)))
127	127
	145	+(((
128	128	2) Flash: work mode, device starts to work and send out console output for further debug
	147	+)))
129	129
130	130
131	131
132	132	=== 1.5.3 Reset Button ===
133	133
	153	+
134	134	Press to reboot the device.
135	135
136	136
...	...	@@ -137,13 +137,18 @@
137	137
138	138	=== 1.5.4 LED ===
139	139
	160	+
140	140	It will flash:
141	141
142	142	1. When boot the device in flash mode
143	143	1. Send an uplink packet
144	144
	166	+
	167	+
	168	+
145	145	= 2.  Use N95S31B to communicate with IoT Server =
146	146
	171	+
147	147	== 2.1  How it works ==
148	148
149	149
...	...	@@ -160,7 +160,7 @@
160	160
161	161	)))
162	162
163		-[[image:1657350248151-650.png]]
	188	+[[image:1657520100595-569.png]]
164	164
165	165	(((
166	166
...	...	@@ -176,26 +176,49 @@
176	176	[[image:image-20220709150546-2.png]]
177	177
178	178
	204	+
179	179	=== 2.2.1 Test Requirement ===
180	180
181	181
	208	+(((
182	182	To use N95S31B in your city, make sure meet below requirements:
	210	+)))
183	183
184		-* Your local operator has already distributed a NB-IoT Network there.
185		-* The local NB-IoT network used the band that N95S31B supports.
186		-* 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	+)))
187	187
	222	+(((
188	188	Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8.
	224	+)))
189	189
	226	+(((
190	190	N95S31B supports different communication protocol such as :
	228	+)))
191	191
192	192	(((
193		-* CoAP  ((% style="color:red" %)120.24.4.116:5683(%%))
194		-* raw UDP  ((% style="color:red" %)120.24.4.116:5601(%%))
195		-* MQTT  ((% style="color:red" %)120.24.4.116:1883(%%))
196		-* 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	+)))
197	197
	244	+(((
198	198	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	+)))
199	199
200	200
201	201	)))
...	...	@@ -206,6 +206,7 @@
206	206
207	207	=== 2.2.3  Insert SIM card ===
208	208
	257	+
209	209	(((
210	210	Insert the NB-IoT Card get from your provider.
211	211	)))
...	...	@@ -221,14 +221,18 @@
221	221
222	222	=== 2.2.4  Connect USB – TTL to N95S31B to configure it ===
223	223
	273	+
224	224	(((
225	225	(((
226	226	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	+
227	227	)))
228	228	)))
229	229
230	230	[[image:1657351312545-300.png]]
231	231
	284	+
232	232	**Connection:**
233	233
234	234	(% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND
...	...	@@ -252,8 +252,9 @@
252	252
253	253	[[image:1657329814315-101.png]]
254	254
	308	+
255	255	(((
256		-(% 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]]**
257	257	)))
258	258
259	259
...	...	@@ -260,9 +260,10 @@
260	260
261	261	=== 2.2.5  Use CoAP protocol to uplink data ===
262	262
263		-(% 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/]]
264	264
	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/]]**
265	265
	320	+
266	266	(((
267	267	**Use below commands:**
268	268	)))
...	...	@@ -301,6 +301,8 @@
301	301	* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/ to set UDP server address and port
302	302	* (% style="color:blue" %)**AT+CFM=1       ** (%%) ~/~/ If the server does not respond, this command is unnecessary
303	303
	359	+
	360	+
304	304	[[image:1657352391268-297.png]]
305	305
306	306
...	...	@@ -310,6 +310,7 @@
310	310
311	311	=== 2.2.7  Use MQTT protocol to uplink data ===
312	312
	370	+
313	313	N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption.
314	314
315	315	* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
...	...	@@ -320,11 +320,14 @@
320	320	* (% style="color:blue" %)**AT+PUBTOPIC=f9527                               **(%%)~/~/Set the sending topic of MQTT
321	321	* (% style="color:blue" %)**AT+SUBTOPIC=Ns9527          **(%%) ~/~/Set the subscription topic of MQTT
322	322
	381	+
	382	+
323	323	[[image:1657352634421-276.png]]
324	324
325	325
326	326	[[image:1657352645687-385.png]]
327	327
	388	+
328	328	(((
329	329	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.
330	330	)))
...	...	@@ -338,11 +338,14 @@
338	338
339	339	=== 2.2.8  Use TCP protocol to uplink data ===
340	340
	402	+
341	341	This feature is supported since firmware version v110
342	342
343	343	* (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/ Set to use TCP protocol to uplink
344	344	* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600   **(%%) ~/~/ to set TCP server address and port
345	345
	408	+
	409	+
346	346	[[image:1657352898400-901.png]]
347	347
348	348
...	...	@@ -352,6 +352,7 @@
352	352
353	353	=== 2.2.9  Change Update Interval ===
354	354
	419	+
355	355	User can use below command to change the (% style="color:green" %)**uplink interval**.
356	356
357	357	* (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
...	...	@@ -365,30 +365,52 @@
365	365	== 2.3  Uplink Payload ==
366	366
367	367
368		-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	+)))
369	369
370	370
	438	+(((
371	371	For example:
	440	+)))
372	372
373		- (% 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	+)))
374	374
375	375
	447	+(((
376	376	The uplink payloads are composed in  ASCII String. For example:
	449	+)))
377	377
	451	+(((
378	378	0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload:
	453	+)))
379	379
	455	+(((
380	380	0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes
	457	+)))
381	381
382	382
	460	+(((
383	383	(% style="color:red" %)**NOTE:**
	462	+)))
384	384
385	385	(% style="color:red" %)
386		-1. All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]].
387		-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.**
388	388
389	389
	472	+
	473	+
	474	+)))
	475	+
390	390	=== 2.3.1  Payload Analyze ===
391	391
	478	+
392	392	N95S31B uplink payload includes in total 21 bytes
393	393
394	394
...	...	@@ -423,6 +423,8 @@
423	423	)))
424	424
425	425	(((
	513	+
	514	+
426	426	(((
427	427	If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data.
428	428	)))
...	...	@@ -455,6 +455,7 @@
455	455
456	456	=== 2.3.2  Device ID ===
457	457
	547	+
458	458	(((
459	459	By default, the Device ID equal to the last 6 bytes of IMEI.
460	460	)))
...	...	@@ -480,14 +480,25 @@
480	480	=== 2.3.3  Version Info ===
481	481
482	482
	573	+(((
483	483	These bytes include the hardware and software version.
	575	+)))
484	484
	577	+(((
485	485	Higher byte: Specify hardware version: always 0x00 for N95S31B
	579	+)))
486	486
	581	+(((
487	487	Lower byte: Specify the software version: 0x6E=110, means firmware version 110
	583	+)))
488	488
	585	+(((
	586	+
	587	+)))
489	489
	589	+(((
490	490	For example: 0x00 6E: this device is N95S31B with firmware version 110.
	591	+)))
491	491
492	492	(((
493	493
...	...	@@ -496,6 +496,7 @@
496	496
497	497	=== 2.3.4  Battery Info ===
498	498
	600	+
499	499	(((
500	500	Ex1: 0x0B45 = 2885mV
501	501	)))
...	...	@@ -508,6 +508,7 @@
508	508
509	509	=== 2.3.5  Signal Strength ===
510	510
	613	+
511	511	(((
512	512	NB-IoT Network signal Strength.
513	513	)))
...	...	@@ -540,6 +540,7 @@
540	540
541	541	=== 2.3.6  Temperature & Humidity ===
542	542
	646	+
543	543	The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server.
544	544
545	545	[[image:image-20220709161741-3.png]]
...	...	@@ -558,8 +558,9 @@
558	558
559	559	== 2.4  Downlink Payload ==
560	560
561		-By default, NDDS75 prints the downlink payload to console port.
562	562
	666	+By default, N95S31B prints the downlink payload to console port.
	667	+
563	563	[[image:image-20220709100028-1.png]]
564	564
565	565
...	...	@@ -596,7 +596,7 @@
596	596	)))
597	597
598	598	(((
599		-If payload = 0x04FF, it will reset the NDDS75
	704	+If payload = 0x04FF, it will reset the N95S31B
600	600	)))
601	601
602	602
...	...	@@ -610,6 +610,7 @@
610	610
611	611	== 2.5  ​Battery Analysis ==
612	612
	718	+
613	613	=== 2.5.1  ​Battery Type ===
614	614
615	615
...	...	@@ -637,8 +637,9 @@
637	637
638	638	=== 2.5.2  Power consumption Analyze ===
639	639
	746	+
640	640	(((
641		-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.
642	642	)))
643	643
644	644	(((
...	...	@@ -648,6 +648,7 @@
648	648
649	649	=== 2.5.3  ​Battery Note ===
650	650
	758	+
651	651	(((
652	652	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.
653	653	)))
...	...	@@ -670,6 +670,7 @@
670	670
671	671	= 3. ​ Access NB-IoT Module =
672	672
	781	+
673	673	(((
674	674	Users can directly access the AT command set of the NB-IoT module.
675	675	)))
...	...	@@ -676,6 +676,8 @@
676	676
677	677	(((
678	678	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	+
679	679	)))
680	680
681	681	[[image:1657333200519-600.png]]
...	...	@@ -684,11 +684,13 @@
684	684
685	685	= 4.  Using the AT Commands =
686	686
	798	+
687	687	== 4.1  Access AT Commands ==
688	688
689		-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/]]
690	690
	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]]
691	691
	804	+
692	692	AT+<CMD>?  : Help on <CMD>
693	693
694	694	AT+<CMD>         : Run <CMD>
...	...	@@ -762,6 +762,7 @@
762	762
763	763	= ​5.  FAQ =
764	764
	878	+
765	765	== 5.1 ​ How to Upgrade Firmware ==
766	766
767	767
...	...	@@ -776,13 +776,16 @@
776	776	(((
777	777
778	778
779		-(% 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.**
780	780	)))
	896	+)))
781	781
782	782
783	783
784	784	= 6.  Trouble Shooting =
785	785
	902	+
786	786	== 6.1  ​Connection problem when uploading firmware ==
787	787
788	788
...	...	@@ -798,6 +798,7 @@
798	798
799	799	== 6.2  AT Command input doesn't work ==
800	800
	918	+
801	801	(((
802	802	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.
803	803
...	...	@@ -847,5 +847,9 @@
847	847
848	848	= 9.  Support =
849	849
	968	+
850	850	* 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.
851	851	* 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