Skip to Content
Last modified by Mengting Qiu on 2024/04/02 16:44
From version 97.3
edited by Xiaoling
on 2022/07/09 11:10
Change comment: There is no comment for this version
To version 115.3
edited by Xiaoling
on 2022/07/09 16:59
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -NDDS75 NB-IoT Distance Detect Sensor User Manual
1 +N95S31B NB-IoT Temperature & Humidity Sensor User Manual
Content
... ... @@ -1,63 +1,60 @@
1 1  (% style="text-align:center" %)
2 -[[image:image-20220709085040-1.png||height="542" width="524"]]
2 +[[image:1657348034241-728.png||height="470" width="470"]]
3 3  
4 4  
5 5  
6 6  
7 7  
8 -**Table of Contents:**
9 9  
10 -{{toc/}}
11 11  
10 +**Table of Contents:**
12 12  
13 13  
14 14  
15 15  
16 16  
16 +
17 17  = 1.  Introduction =
18 18  
19 -== 1.1 ​ What is NDDS75 Distance Detection Sensor ==
19 +== 1.1 ​ What is N95S31B NB-IoT Sensor Node ==
20 20  
21 21  (((
22 22  
23 23  
24 -(((
25 -The Dragino NDDS75 is a (% style="color:blue" %)**NB-IoT Distance Detection Sensor**(%%) for Internet of Things solution. It is designed to measure the distance between the sensor and a flat object. The distance detection sensor is a module that uses ultrasonic sensing technology for distance measurement, and temperature compensation is performed internally to improve the reliability of data.
26 -\\The NDDS75 can be applied to scenarios such as horizontal distance measurement, liquid level measurement, parking management system, object proximity and presence detection, intelligent trash can management system, robot obstacle avoidance, automatic control, sewer, bottom water level monitoring, etc. It detects the distance between the measured object and the sensor, and uploads the value via wireless to IoT Server via NB-IoT Network.
27 -\\NarrowBand-Internet of Things (NB-IoT) is a standards-based low power wide area (LPWA) technology developed to enable a wide range of new IoT devices and services. NB-IoT significantly improves the power consumption of user devices, system capacity and spectrum efficiency, especially in deep coverage.
28 -\\NDDS75 supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP and CoAP** (%%)for different application requirement.
29 -\\NDDS75 is powered by (% style="color:blue" %)**8500mAh Li-SOCI2 battery**(%%), It is designed for long term use up to 5 years. (Actually Battery life depends on the use environment, update period & uplink method)
30 -\\To use NDDS75, user needs to check if there is NB-IoT coverage in local area and with the bands NDDS75 supports. If the local operate support it, user needs to get a NB-IoT SIM card from local operator and install NDDS75 to get NB-IoT network connection.
31 -)))
24 +The Dragino N95S31B is a (% style="color:blue" %)**NB-IoT Temperature and Humidity Sensor**(%%) for Internet of Things solution. It is used to measure the (% style="color:blue" %)**surrounding environment temperature and relative air humidity precisely**(%%), and then upload to IoT server via NB-IoT network*.
32 32  
33 -
34 -)))
26 +The temperature & humidity sensor used in N95S31B is SHT31, which is fully calibrated, linearized, and temperature compensated digital output from Sensirion, it provides a strong reliability and long-term stability. The SHT31 is fixed in a (% style="color:blue" %)**waterproof anti-condensation casing **(%%)for long term use.
35 35  
36 -[[image:1654503236291-817.png]]
28 +N95S31B supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP and CoAP**(%%) for different application requirement.
37 37  
30 +N95S31B is powered by(% style="color:blue" %)**8500mAh Li-SOCI2 battery**(%%), It is designed for long term use up to several years. (Real-world battery life depends on the use environment, update period. Please check related Power Analyze report).
38 38  
39 -[[image:1657327959271-447.png]]
40 40  
33 +~* make sure you have NB-IoT coverage locally.
41 41  
35 +
36 +)))
42 42  
43 -== 1.2 ​ Features ==
38 +[[image:1657348284168-431.png]]
44 44  
45 45  
41 +
42 +== 1.2 ​ Features ==
43 +
46 46  * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD
47 -* Ultra low power consumption
48 -* Distance Detection by Ultrasonic technology
49 -* Flat object range 280mm - 7500mm
50 -* Accuracy: ±(1cm+S*0.3%) (S: Distance)
51 -* Cable Length: 25cm
45 +* Monitor Temperature & Humidity via SHT31
52 52  * AT Commands to change parameters
53 53  * Uplink on periodically
54 54  * Downlink to change configure
55 55  * IP66 Waterproof Enclosure
50 +* Ultra-Low Power consumption
51 +* AT Commands to change parameters
56 56  * Micro SIM card slot for NB-IoT SIM
57 57  * 8500mAh Battery for long term use
58 58  
59 59  
60 60  
57 +
61 61  == 1.3  Specification ==
62 62  
63 63  
... ... @@ -77,6 +77,7 @@
77 77  
78 78  (% style="color:#037691" %)**Battery:**
79 79  
77 +
80 80  * Li/SOCI2 un-chargeable battery
81 81  * Capacity: 8500mAh
82 82  * Self Discharge: <1% / Year @ 25°C
... ... @@ -83,13 +83,9 @@
83 83  * Max continuously current: 130mA
84 84  * Max boost current: 2A, 1 second
85 85  
86 -(% style="color:#037691" %)**Power Consumption**
87 87  
88 -* STOP Mode: 10uA @ 3.3v
89 -* Max transmit power: [[350mA@3.3v>>mailto:350mA@3.3v]]
90 90  
91 91  
92 -
93 93  == ​1.4  Applications ==
94 94  
95 95  * Smart Buildings & Home Automation
... ... @@ -105,22 +105,51 @@
105 105  
106 106  == 1.5  Pin Definitions ==
107 107  
102 +N95S31B use the mother board from NBSN95 which as below.
108 108  
109 -[[image:1657328609906-564.png]]
104 +[[image:image-20220709144723-1.png]]
110 110  
111 111  
107 +=== 1.5.1 Jumper JP2 ===
112 112  
113 -= 2.  Use NDDS75 to communicate with IoT Server =
109 +Power on Device when put this jumper.
114 114  
111 +
112 +
113 +=== 1.5.2 BOOT MODE / SW1 ===
114 +
115 +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.
116 +
117 +2) Flash: work mode, device starts to work and send out console output for further debug
118 +
119 +
120 +
121 +=== 1.5.3 Reset Button ===
122 +
123 +Press to reboot the device.
124 +
125 +
126 +
127 +=== 1.5.4 LED ===
128 +
129 +It will flash:
130 +
131 +1. When boot the device in flash mode
132 +1. Send an uplink packet
133 +
134 +
135 += 2.  Use N95S31B to communicate with IoT Server =
136 +
115 115  == 2.1  How it works ==
116 116  
139 +
117 117  (((
118 -The NDDS75 is equipped with a NB-IoT module, the pre-loaded firmware in NDDS75 will get environment data from sensors and send the value to local NB-IoT network via the NB-IoT module.  The NB-IoT network will forward this value to IoT server via the protocol defined by NDDS75.
141 +The N95S31B is equipped with a NB-IoT module, the pre-loaded firmware in N95S31B will get environment data from sensors and send the value to local NB-IoT network via the NB-IoT module.  The NB-IoT network will forward this value to IoT server via the protocol defined by N95S31B.
119 119  )))
120 120  
121 121  
122 122  (((
123 -The diagram below shows the working flow in default firmware of NDDS75:
146 +The diagram below shows the working flow in default firmware of N95S31B:
124 124  )))
125 125  
126 126  (((
... ... @@ -127,7 +127,7 @@
127 127  
128 128  )))
129 129  
130 -[[image:1657328659945-416.png]]
153 +[[image:1657350248151-650.png]]
131 131  
132 132  (((
133 133  
... ... @@ -134,30 +134,45 @@
134 134  )))
135 135  
136 136  
137 -== 2.2 ​ Configure the NDDS75 ==
160 +== 2.2 ​ Configure the N95S31B ==
138 138  
139 139  
163 +=== 2.2.1  Power On N95S31B ===
164 +
165 +
166 +[[image:image-20220709150546-2.png]]
167 +
168 +
140 140  === 2.2.1 Test Requirement ===
141 141  
142 -(((
143 -To use NDDS75 in your city, make sure meet below requirements:
144 -)))
145 145  
172 +To use N95S31B in your city, make sure meet below requirements:
173 +
146 146  * Your local operator has already distributed a NB-IoT Network there.
147 -* The local NB-IoT network used the band that NSE01 supports.
175 +* The local NB-IoT network used the band that N95S31B supports.
148 148  * Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
149 149  
178 +Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8.
179 +
180 +N95S31B supports different communication protocol such as :
181 +
150 150  (((
151 -Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8.  The NDDS75 will use CoAP((% style="color:red" %)120.24.4.116:5683)(%%) or raw UDP((% style="color:red" %)120.24.4.116:5601)(%%) or MQTT((% style="color:red" %)120.24.4.116:1883)(%%)or TCP((% style="color:red" %)120.24.4.116:5600)(%%)protocol to send data to the test server
152 -)))
183 +* CoAP  ((% style="color:red" %)120.24.4.116:5683(%%))
184 +* raw UDP  ((% style="color:red" %)120.24.4.116:5601(%%))
185 +* MQTT  ((% style="color:red" %)120.24.4.116:1883(%%))
186 +* TCP  ((% style="color:red" %)120.24.4.116:5600(%%))
153 153  
188 +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.
154 154  
155 -[[image:1657328756309-230.png]]
190 +
191 +)))
156 156  
193 +[[image:1657350625843-586.png]]
157 157  
158 158  
159 -=== 2.2.2 Insert SIM card ===
160 160  
197 +=== 2.2.3  Insert SIM card ===
198 +
161 161  (((
162 162  Insert the NB-IoT Card get from your provider.
163 163  )))
... ... @@ -167,19 +167,19 @@
167 167  )))
168 168  
169 169  
170 -[[image:1657328884227-504.png]]
208 +[[image:1657351240556-536.png]]
171 171  
172 172  
173 173  
174 -=== 2.2.3 Connect USB – TTL to NDDS75 to configure it ===
212 +=== 2.2.4  Connect USB – TTL to N95S31B to configure it ===
175 175  
176 176  (((
177 177  (((
178 -User need to configure NDDS75 via serial port to set the (% style="color:blue" %)**Server Address** / **Uplink Topic** (%%)to define where and how-to uplink packets. NDDS75 support AT Commands, user can use a USB to TTL adapter to connect to NDDS75 and use AT Commands to configure it, as below.
216 +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.
179 179  )))
180 180  )))
181 181  
182 -[[image:image-20220709092052-2.png]]
220 +[[image:1657351312545-300.png]]
183 183  
184 184  **Connection:**
185 185  
... ... @@ -199,90 +199,110 @@
199 199  * Flow Control: (% style="color:green" %)**None**
200 200  
201 201  (((
202 -Make sure the switch is in FLASH position, then power on device by connecting the jumper on NDDS75. NDDS75 will output system info once power on as below, we can enter the (% style="color:green" %)**password: 12345678**(%%) to access AT Command input.
240 +Make sure the switch is in FLASH position, then power on device by connecting the jumper on N95S31B. N95S31B will output system info once power on as below, we can enter the (% style="color:green" %)**password: 12345678**(%%) to access AT Command input.
203 203  )))
204 204  
205 205  [[image:1657329814315-101.png]]
206 206  
207 207  (((
208 -(% style="color:red" %)Note: the valid AT Commands can be found at: (%%)[[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/]]
246 +(% 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/]]
209 209  )))
210 210  
211 211  
212 212  
213 -=== 2.2.4 Use CoAP protocol to uplink data ===
251 +=== 2.2.5  Use CoAP protocol to uplink data ===
214 214  
215 215  (% 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/]]
216 216  
217 217  
256 +(((
218 218  **Use below commands:**
258 +)))
219 219  
220 -* (% style="color:blue" %)**AT+PRO=1**  (%%) ~/~/ Set to use CoAP protocol to uplink
221 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%)~/~/ to set CoAP server address and port
222 -* (% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path
260 +* (((
261 +(% style="color:blue" %)**AT+PRO=1**  (%%) ~/~/ Set to use CoAP protocol to uplink
262 +)))
263 +* (((
264 +(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%)~/~/ to set CoAP server address and port
265 +)))
266 +* (((
267 +(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path
268 +)))
223 223  
270 +(((
271 +
272 +
224 224  For parameter description, please refer to AT command set
274 +)))
225 225  
226 -[[image:1657330452568-615.png]]
276 +[[image:1657352146020-183.png]]
227 227  
228 228  
279 +(((
229 229  After configure the server address and (% style="color:green" %)**reset the device**(%%) (via AT+ATZ ), NDDS75 will start to uplink sensor values to CoAP server.
281 +)))
230 230  
231 -[[image:1657330472797-498.png]]
283 +[[image:1657352185396-303.png]]
232 232  
233 233  
234 234  
235 -=== 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
287 +=== 2.2.6  Use UDP protocol to uplink data(Default protocol) ===
236 236  
237 237  
238 -* (% style="color:blue" %)**AT+PRO=2   ** (%%) ~/~/ Set to use UDP protocol to uplink
290 +* (% style="color:blue" %)**AT+PRO=2   ** (%%) ~/~/ Set to use UDP protocol to uplink
239 239  * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/ to set UDP server address and port
240 -* (% style="color:blue" %)**AT+CFM=1       ** (%%) ~/~/If the server does not respond, this command is unnecessary
292 +* (% style="color:blue" %)**AT+CFM=1       ** (%%) ~/~/ If the server does not respond, this command is unnecessary
241 241  
242 -[[image:1657330501006-241.png]]
294 +[[image:1657352391268-297.png]]
243 243  
244 244  
245 -[[image:1657330533775-472.png]]
297 +[[image:1657352403317-397.png]]
246 246  
247 247  
248 248  
249 -=== 2.2.6 Use MQTT protocol to uplink data ===
301 +=== 2.2.7  Use MQTT protocol to uplink data ===
250 250  
303 +N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption.
251 251  
252 -* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
253 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/Set MQTT server address and port
254 -* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/Set up the CLIENT of MQTT
255 -* (% style="color:blue" %)**AT+UNAME=UNAME                               **(%%)~/~/Set the username of MQTT
256 -* (% style="color:blue" %)**AT+PWD=PWD                                        **(%%)~/~/Set the password of MQTT
257 -* (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB                 **(%%)~/~/Set the sending topic of MQTT
258 -* (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB          **(%%) ~/~/Set the subscription topic of MQTT
305 +* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
306 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/Set MQTT server address and port
307 +* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/Set up the CLIENT of MQTT
308 +* (% style="color:blue" %)**AT+UNAME=UNAME                                **(%%)~/~/Set the username of MQTT
309 +* (% style="color:blue" %)**AT+PWD=PWD                                         **(%%)~/~/Set the password of MQTT
310 +* (% style="color:blue" %)**AT+PUBTOPIC=f9527                               **(%%)~/~/Set the sending topic of MQTT
311 +* (% style="color:blue" %)**AT+SUBTOPIC=Ns9527          **(%%) ~/~/Set the subscription topic of MQTT
259 259  
260 -[[image:1657249978444-674.png]]
313 +[[image:1657352634421-276.png]]
261 261  
262 262  
263 -[[image:1657330723006-866.png]]
316 +[[image:1657352645687-385.png]]
264 264  
318 +(((
319 +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.
320 +)))
265 265  
322 +
266 266  (((
267 -MQTT protocol has a much higher power consumption compare vs UDP / CoAP protocol. Please check the power analyze document and adjust the uplink period to a suitable interval.
324 +MQTT protocol has a much high-power consumption compare vs UDP / CoAP protocol. Please check the power analyze document and adjust the uplink period to a suitable interval.
268 268  )))
269 269  
270 270  
271 271  
272 -=== 2.2.7 Use TCP protocol to uplink data ===
329 +=== 2.2.8  Use TCP protocol to uplink data ===
273 273  
331 +This feature is supported since firmware version v110
274 274  
275 275  * (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/ Set to use TCP protocol to uplink
276 276  * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600   **(%%) ~/~/ to set TCP server address and port
277 277  
278 -[[image:image-20220709093918-1.png]]
336 +[[image:1657352898400-901.png]]
279 279  
280 280  
281 -[[image:image-20220709093918-2.png]]
339 +[[image:1657352914475-252.png]]
282 282  
283 283  
284 284  
285 -=== 2.2.8 Change Update Interval ===
343 +=== 2.2.9  Change Update Interval ===
286 286  
287 287  User can use below command to change the (% style="color:green" %)**uplink interval**.
288 288  
... ... @@ -289,69 +289,92 @@
289 289  * (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
290 290  
291 291  (((
292 -(% style="color:red" %)**NOTE:**
350 +
293 293  )))
294 294  
295 -(((
296 -(% style="color:red" %)1. By default, the device will send an uplink message every 1 hour.
297 -)))
298 298  
299 299  
300 -
301 301  == 2.3  Uplink Payload ==
302 302  
303 -In this mode, uplink payload includes in total 14 bytes
304 304  
358 +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.
305 305  
306 -(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:510px" %)
307 -|=(% style="width: 80px;" %)(((
308 -**Size(bytes)**
309 -)))|=(% style="width: 80px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 110px;" %)**1**|=(% style="width: 110px;" %)**2**|=(% style="width: 70px;" %)**1**
310 -|(% style="width:97px" %)**Value**|(% style="width:83px" %)[[Device ID>>||anchor="H2.4.1A0A0DeviceID"]]|(% style="width:41px" %)[[Ver>>||anchor="H2.4.2A0VersionInfo"]]|(% style="width:46px" %)[[BAT>>||anchor="H2.4.3A0BatteryInfo"]]|(% style="width:123px" %)[[Signal Strength>>||anchor="H2.4.4A0SignalStrength"]]|(% style="width:120px" %)[[Distance (unit: mm)>>||anchor="H2.4.5A0Distance"]]|(% style="width:80px" %)[[Interrupt>>||anchor="H2.4.6A0DigitalInterrupt"]]
311 311  
312 -(((
313 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS751 uplink data.
314 -)))
361 +For example:
315 315  
363 + (% 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.
316 316  
317 -[[image:1657331036973-987.png]]
318 318  
319 -(((
320 -The payload is ASCII string, representative same HEX:
321 -)))
366 +The uplink payloads are composed in  ASCII String. For example:
322 322  
323 -(((
324 -0x72403155615900640c6c19029200 where:
325 -)))
368 +0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload:
326 326  
327 -* (((
328 -Device ID: 0x724031556159 = 724031556159
370 +0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes
371 +
372 +
373 +(% style="color:red" %)**NOTE:**
374 +
375 +(% style="color:red" %)
376 +1. All modes share the same Payload Explanation from [[HERE>>path:#Payload_Explain]].
377 +1. By default, the device will send an uplink message every 1 hour.
378 +
379 +
380 +
381 +=== 2.3.1  Payload Analyze ===
382 +
383 +N95S31B uplink payload includes in total 21 bytes
384 +
385 +
386 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %)
387 +|=(% style="width: 60px;" %)(((
388 +**Size(bytes)**
389 +)))|=(% style="width: 60px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 80px;" %)**1**|=(% style="width: 80px;" %) |=(% style="width: 99px;" %) |=(% style="width: 77px;" %)**2**|=(% style="width: 60px;" %)**1**
390 +|(% style="width:97px" %)**Value**|(% style="width:83px" %)[[Device ID>>||anchor="H2.4.1A0A0DeviceID"]]|(% style="width:41px" %)[[Ver>>||anchor="H2.4.2A0VersionInfo"]]|(% style="width:46px" %)[[BAT>>||anchor="H2.4.3A0BatteryInfo"]]|(% style="width:123px" %)[[Signal Strength>>||anchor="H2.4.4A0SignalStrength"]]|(% style="width:123px" %)MOD 0X01|(% style="width:99px" %)(((
391 +Reserve/ Same as NBSN95 CFGMOD=1
392 +
393 +No function here.
394 +)))|(% style="width:77px" %)(((
395 +[[Temperature >>||anchor="H2.4.5A0Distance"]]
396 +
397 +By SHT31
398 +)))|(% style="width:80px" %)(((
399 +[[Humidity>>||anchor="H2.4.6A0DigitalInterrupt"]]
400 +
401 +By SHT31
329 329  )))
330 -* (((
331 -Version: 0x0064=100=1.0.0
332 -)))
333 333  
334 -* (((
335 -BAT: 0x0c6c = 3180 mV = 3.180V
404 +(((
405 +(((
406 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data.
336 336  )))
337 -* (((
338 -Signal: 0x19 = 25
339 339  )))
340 -* (((
341 -Distance: 0x0292= 658 mm
342 -)))
343 -* (((
344 -Interrupt: 0x00 = 0
345 345  
346 346  
411 +[[image:1657354294009-643.png]]
347 347  
413 +
414 +The payload is ASCII string, representative same HEX: 0x724031607457006e0ccd1b0100dc000ccc00e10186 where:
415 +
416 +* Device ID: 0x724031607457 = 724031607457
417 +* Version: 0x006e=110=1.1.0
418 +
419 +* BAT: 0x0ccd = 3277 mV = 3.277V
420 +* Signal: 0x1b = 27
421 +* Model: 0x01 = 1
422 +* 0x00dc000ccc= reserve, ignore in N95S31B
423 +* Temperature by SHT31: 0x00e1 = 225 = 22.5 °C
424 +* Humidity by SHT31: 0x0186 = 390 = 39.0 %rh
425 +
426 +(((
348 348  
349 349  )))
350 350  
351 -== 2.4  Payload Explanation and Sensor Interface ==
430 +(((
431 +
432 +)))
352 352  
353 353  
354 -=== 2.4.1  Device ID ===
435 +=== 2.3.2  Device ID ===
355 355  
356 356  (((
357 357  By default, the Device ID equal to the last 6 bytes of IMEI.
... ... @@ -375,24 +375,25 @@
375 375  
376 376  
377 377  
378 -=== 2.4.2  Version Info ===
459 +=== 2.3.3  Version Info ===
379 379  
380 -(((
381 -Specify the software version: 0x64=100, means firmware version 1.00.
382 -)))
383 383  
384 -(((
385 -For example: 0x00 64 : this device is NDDS75 with firmware version 1.0.0.
386 -)))
462 +These bytes include the hardware and software version.
387 387  
464 +Higher byte: Specify hardware version: always 0x00 for N95S31B
388 388  
466 +Lower byte: Specify the software version: 0x6E=110, means firmware version 110
389 389  
390 -=== 2.4.3  Battery Info ===
391 391  
469 +For example: 0x00 6E: this device is N95S31B with firmware version 110.
470 +
392 392  (((
393 -Check the battery voltage for LSE01.
472 +
394 394  )))
395 395  
475 +
476 +=== 2.3.4  Battery Info ===
477 +
396 396  (((
397 397  Ex1: 0x0B45 = 2885mV
398 398  )))
... ... @@ -403,7 +403,7 @@
403 403  
404 404  
405 405  
406 -=== 2.4.4  Signal Strength ===
488 +=== 2.3.5  Signal Strength ===
407 407  
408 408  (((
409 409  NB-IoT Network signal Strength.
... ... @@ -435,81 +435,24 @@
435 435  
436 436  
437 437  
438 -=== 2.4.5  Distance ===
520 +=== 2.3.6  Temperature & Humidity ===
439 439  
440 -Get the distance. Flat object range 280mm - 7500mm.
522 +The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server.
441 441  
442 -For example, if the data you get from the register is **__0x0B 0x05__**, the distance between the sensor and the measured object is
524 +[[image:image-20220709161741-3.png]]
443 443  
444 -(((
445 -(((
446 -(% style="color:blue" %)** 0B05(H) = 2821(D) = 2821mm.**
447 -)))
448 -)))
449 449  
450 -(((
451 -
452 -)))
527 +Convert the read byte to decimal and divide it by ten.
453 453  
454 -(((
455 -
456 -)))
457 457  
458 -=== 2.4.6  Digital Interrupt ===
530 +**Example:**
459 459  
460 -(((
461 -Digital Interrupt refers to pin (% style="color:blue" %)**GPIO_EXTI**(%%), and there are different trigger methods. When there is a trigger, the NDDS75 will send a packet to the server.
462 -)))
532 +Temperature:  Read:00ec (H) = 236(D)  Value:  236 /10=23.6℃
463 463  
464 -(((
465 -The command is:
466 -)))
534 +Humidity:    Read:0295(H)=661(D)    Value:  661 / 10=66.1, So 66.1%
467 467  
468 -(((
469 -(% style="color:blue" %)**AT+INTMOD=3 **(%%) ~/~/(more info about INMOD please refer [[**AT Command Manual**>>url:https://www.dragino.com/downloads/downloads/NB-IoT/NBSN95/DRAGINO_NBSN95-NB_AT%20Commands_v1.1.0.pdf]])**.**
470 -)))
471 471  
472 472  
473 -(((
474 -The lower four bits of this data field shows if this packet is generated by interrupt or not. Click here for the hardware and software set up.
475 -)))
476 -
477 -
478 -(((
479 -Example:
480 -)))
481 -
482 -(((
483 -0x(00): Normal uplink packet.
484 -)))
485 -
486 -(((
487 -0x(01): Interrupt Uplink Packet.
488 -)))
489 -
490 -
491 -
492 -=== 2.4.7  ​+5V Output ===
493 -
494 -(((
495 -NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling. 
496 -)))
497 -
498 -
499 -(((
500 -The 5V output time can be controlled by AT Command.
501 -)))
502 -
503 -(((
504 -(% style="color:blue" %)**AT+5VT=1000**
505 -)))
506 -
507 -(((
508 -Means set 5V valid time to have 1000ms. So the real 5V output will actually have 1000ms + sampling time for other sensors.
509 -)))
510 -
511 -
512 -
513 513  == 2.5  Downlink Payload ==
514 514  
515 515  By default, NDDS75 prints the downlink payload to console port.
... ... @@ -582,7 +582,9 @@
582 582  == 2.7  ​Firmware Change Log ==
583 583  
584 584  
610 +(((
585 585  Download URL & Firmware Change log
612 +)))
586 586  
587 587  (((
588 588  [[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/Firmware/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/Firmware/]]
... ... @@ -589,7 +589,9 @@
589 589  )))
590 590  
591 591  
619 +(((
592 592  Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
621 +)))
593 593  
594 594  
595 595  
1657348034241-728.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +127.8 KB
Content
1657348284168-431.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +93.5 KB
Content
1657350248151-650.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +126.1 KB
Content
1657350625843-586.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +93.3 KB
Content
1657351240556-536.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +483.6 KB
Content
1657351312545-300.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +675.8 KB
Content
1657352146020-183.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +264.0 KB
Content
1657352185396-303.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +98.3 KB
Content
1657352391268-297.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +238.0 KB
Content
1657352403317-397.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +547.7 KB
Content
1657352634421-276.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +163.6 KB
Content
1657352645687-385.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +214.7 KB
Content
1657352898400-901.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +144.8 KB
Content
1657352914475-252.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +157.0 KB
Content
1657354294009-643.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +214.7 KB
Content
image-20220709144723-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +413.1 KB
Content
image-20220709150546-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +333.5 KB
Content
image-20220709161741-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +111.2 KB
Content