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,14 +127,20 @@
127	127
128	128	=== 1.5.2 BOOT MODE / SW1 ===
129	129
	140	+
	141	+(((
130	130	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	+)))
131	131
	145	+(((
132	132	2) Flash: work mode, device starts to work and send out console output for further debug
	147	+)))
133	133
134	134
135	135
136	136	=== 1.5.3 Reset Button ===
137	137
	153	+
138	138	Press to reboot the device.
139	139
140	140
...	...	@@ -141,13 +141,18 @@
141	141
142	142	=== 1.5.4 LED ===
143	143
	160	+
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
	166	+
	167	+
	168	+
149	149	= 2.  Use N95S31B to communicate with IoT Server =
150	150
	171	+
151	151	== 2.1  How it works ==
152	152
153	153
...	...	@@ -164,7 +164,7 @@
164	164
165	165	)))
166	166
167		-[[image:1657350248151-650.png]]
	188	+[[image:1657520100595-569.png]]
168	168
169	169	(((
170	170
...	...	@@ -180,26 +180,49 @@
180	180	[[image:image-20220709150546-2.png]]
181	181
182	182
	204	+
183	183	=== 2.2.1 Test Requirement ===
184	184
185	185
	208	+(((
186	186	To use N95S31B in your city, make sure meet below requirements:
	210	+)))
187	187
188		-* Your local operator has already distributed a NB-IoT Network there.
189		-* The local NB-IoT network used the band that N95S31B supports.
190		-* 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	+)))
191	191
	222	+(((
192	192	Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8.
	224	+)))
193	193
	226	+(((
194	194	N95S31B supports different communication protocol such as :
	228	+)))
195	195
196	196	(((
197		-* CoAP  ((% style="color:red" %)120.24.4.116:5683(%%))
198		-* raw UDP  ((% style="color:red" %)120.24.4.116:5601(%%))
199		-* MQTT  ((% style="color:red" %)120.24.4.116:1883(%%))
200		-* 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	+)))
201	201
	244	+(((
202	202	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	+)))
203	203
204	204
205	205	)))
...	...	@@ -210,6 +210,7 @@
210	210
211	211	=== 2.2.3  Insert SIM card ===
212	212
	257	+
213	213	(((
214	214	Insert the NB-IoT Card get from your provider.
215	215	)))
...	...	@@ -225,14 +225,18 @@
225	225
226	226	=== 2.2.4  Connect USB – TTL to N95S31B to configure it ===
227	227
	273	+
228	228	(((
229	229	(((
230	230	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	+
231	231	)))
232	232	)))
233	233
234	234	[[image:1657351312545-300.png]]
235	235
	284	+
236	236	**Connection:**
237	237
238	238	(% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND
...	...	@@ -256,8 +256,9 @@
256	256
257	257	[[image:1657329814315-101.png]]
258	258
	308	+
259	259	(((
260		-(% 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]]**
261	261	)))
262	262
263	263
...	...	@@ -264,9 +264,10 @@
264	264
265	265	=== 2.2.5  Use CoAP protocol to uplink data ===
266	266
267		-(% 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/]]
268	268
	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/]]**
269	269
	320	+
270	270	(((
271	271	**Use below commands:**
272	272	)))
...	...	@@ -305,6 +305,8 @@
305	305	* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/ to set UDP server address and port
306	306	* (% style="color:blue" %)**AT+CFM=1       ** (%%) ~/~/ If the server does not respond, this command is unnecessary
307	307
	359	+
	360	+
308	308	[[image:1657352391268-297.png]]
309	309
310	310
...	...	@@ -314,6 +314,7 @@
314	314
315	315	=== 2.2.7  Use MQTT protocol to uplink data ===
316	316
	370	+
317	317	N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption.
318	318
319	319	* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
...	...	@@ -324,11 +324,14 @@
324	324	* (% style="color:blue" %)**AT+PUBTOPIC=f9527                               **(%%)~/~/Set the sending topic of MQTT
325	325	* (% style="color:blue" %)**AT+SUBTOPIC=Ns9527          **(%%) ~/~/Set the subscription topic of MQTT
326	326
	381	+
	382	+
327	327	[[image:1657352634421-276.png]]
328	328
329	329
330	330	[[image:1657352645687-385.png]]
331	331
	388	+
332	332	(((
333	333	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.
334	334	)))
...	...	@@ -342,11 +342,14 @@
342	342
343	343	=== 2.2.8  Use TCP protocol to uplink data ===
344	344
	402	+
345	345	This feature is supported since firmware version v110
346	346
347	347	* (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/ Set to use TCP protocol to uplink
348	348	* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600   **(%%) ~/~/ to set TCP server address and port
349	349
	408	+
	409	+
350	350	[[image:1657352898400-901.png]]
351	351
352	352
...	...	@@ -356,6 +356,7 @@
356	356
357	357	=== 2.2.9  Change Update Interval ===
358	358
	419	+
359	359	User can use below command to change the (% style="color:green" %)**uplink interval**.
360	360
361	361	* (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
...	...	@@ -369,30 +369,52 @@
369	369	== 2.3  Uplink Payload ==
370	370
371	371
372		-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	+)))
373	373
374	374
	438	+(((
375	375	For example:
	440	+)))
376	376
377		- (% 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	+)))
378	378
379	379
	447	+(((
380	380	The uplink payloads are composed in  ASCII String. For example:
	449	+)))
381	381
	451	+(((
382	382	0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload:
	453	+)))
383	383
	455	+(((
384	384	0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes
	457	+)))
385	385
386	386
	460	+(((
387	387	(% style="color:red" %)**NOTE:**
	462	+)))
388	388
389	389	(% style="color:red" %)
390		-1. All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]].
391		-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.**
392	392
393	393
	472	+
	473	+
	474	+)))
	475	+
394	394	=== 2.3.1  Payload Analyze ===
395	395
	478	+
396	396	N95S31B uplink payload includes in total 21 bytes
397	397
398	398
...	...	@@ -427,6 +427,8 @@
427	427	)))
428	428
429	429	(((
	513	+
	514	+
430	430	(((
431	431	If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data.
432	432	)))
...	...	@@ -459,6 +459,7 @@
459	459
460	460	=== 2.3.2  Device ID ===
461	461
	547	+
462	462	(((
463	463	By default, the Device ID equal to the last 6 bytes of IMEI.
464	464	)))
...	...	@@ -484,14 +484,25 @@
484	484	=== 2.3.3  Version Info ===
485	485
486	486
	573	+(((
487	487	These bytes include the hardware and software version.
	575	+)))
488	488
	577	+(((
489	489	Higher byte: Specify hardware version: always 0x00 for N95S31B
	579	+)))
490	490
	581	+(((
491	491	Lower byte: Specify the software version: 0x6E=110, means firmware version 110
	583	+)))
492	492
	585	+(((
	586	+
	587	+)))
493	493
	589	+(((
494	494	For example: 0x00 6E: this device is N95S31B with firmware version 110.
	591	+)))
495	495
496	496	(((
497	497
...	...	@@ -500,6 +500,7 @@
500	500
501	501	=== 2.3.4  Battery Info ===
502	502
	600	+
503	503	(((
504	504	Ex1: 0x0B45 = 2885mV
505	505	)))
...	...	@@ -512,6 +512,7 @@
512	512
513	513	=== 2.3.5  Signal Strength ===
514	514
	613	+
515	515	(((
516	516	NB-IoT Network signal Strength.
517	517	)))
...	...	@@ -544,6 +544,7 @@
544	544
545	545	=== 2.3.6  Temperature & Humidity ===
546	546
	646	+
547	547	The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server.
548	548
549	549	[[image:image-20220709161741-3.png]]
...	...	@@ -562,8 +562,9 @@
562	562
563	563	== 2.4  Downlink Payload ==
564	564
565		-By default, NDDS75 prints the downlink payload to console port.
566	566
	666	+By default, N95S31B prints the downlink payload to console port.
	667	+
567	567	[[image:image-20220709100028-1.png]]
568	568
569	569
...	...	@@ -600,7 +600,7 @@
600	600	)))
601	601
602	602	(((
603		-If payload = 0x04FF, it will reset the NDDS75
	704	+If payload = 0x04FF, it will reset the N95S31B
604	604	)))
605	605
606	606
...	...	@@ -614,6 +614,7 @@
614	614
615	615	== 2.5  ​Battery Analysis ==
616	616
	718	+
617	617	=== 2.5.1  ​Battery Type ===
618	618
619	619
...	...	@@ -641,8 +641,9 @@
641	641
642	642	=== 2.5.2  Power consumption Analyze ===
643	643
	746	+
644	644	(((
645		-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.
646	646	)))
647	647
648	648	(((
...	...	@@ -652,6 +652,7 @@
652	652
653	653	=== 2.5.3  ​Battery Note ===
654	654
	758	+
655	655	(((
656	656	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.
657	657	)))
...	...	@@ -674,6 +674,7 @@
674	674
675	675	= 3. ​ Access NB-IoT Module =
676	676
	781	+
677	677	(((
678	678	Users can directly access the AT command set of the NB-IoT module.
679	679	)))
...	...	@@ -680,6 +680,8 @@
680	680
681	681	(((
682	682	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	+
683	683	)))
684	684
685	685	[[image:1657333200519-600.png]]
...	...	@@ -688,11 +688,13 @@
688	688
689	689	= 4.  Using the AT Commands =
690	690
	798	+
691	691	== 4.1  Access AT Commands ==
692	692
693		-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/]]
694	694
	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]]
695	695
	804	+
696	696	AT+<CMD>?  : Help on <CMD>
697	697
698	698	AT+<CMD>         : Run <CMD>
...	...	@@ -766,6 +766,7 @@
766	766
767	767	= ​5.  FAQ =
768	768
	878	+
769	769	== 5.1 ​ How to Upgrade Firmware ==
770	770
771	771
...	...	@@ -780,13 +780,16 @@
780	780	(((
781	781
782	782
783		-(% 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.**
784	784	)))
	896	+)))
785	785
786	786
787	787
788	788	= 6.  Trouble Shooting =
789	789
	902	+
790	790	== 6.1  ​Connection problem when uploading firmware ==
791	791
792	792
...	...	@@ -802,6 +802,7 @@
802	802
803	803	== 6.2  AT Command input doesn't work ==
804	804
	918	+
805	805	(((
806	806	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.
807	807
...	...	@@ -851,5 +851,9 @@
851	851
852	852	= 9.  Support =
853	853
	968	+
854	854	* 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.
855	855	* 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