Changes for page N95S31B -- NB-IoT Temperature & Humidity Sensor User Manual
Last modified by Mengting Qiu on 2024/04/02 16:44
Summary
-
Page properties (1 modified, 0 added, 0 removed)
-
Attachments (0 modified, 0 added, 21 removed)
- 1657348284168-431.png
- 1657350248151-650.png
- 1657350625843-586.png
- 1657351240556-536.png
- 1657351312545-300.png
- 1657352146020-183.png
- 1657352185396-303.png
- 1657352391268-297.png
- 1657352403317-397.png
- 1657352634421-276.png
- 1657352645687-385.png
- 1657352898400-901.png
- 1657352914475-252.png
- 1657354294009-643.png
- 1657520100595-569.png
- image-20220709144723-1.png
- image-20220709150546-2.png
- image-20220709161741-3.png
- image-20220908154949-1.png
- image-20220908163102-2.png
- image-20221009001045-1.png
Details
- Page properties
-
- Content
-
... ... @@ -1,12 +1,10 @@ 1 1 (% style="text-align:center" %) 2 -[[image: 1657348034241-728.png||height="470" width="470"]]2 +[[image:image-20220709085040-1.png||height="542" width="524"]] 3 3 4 4 5 5 6 6 7 7 8 - 9 - 10 10 **Table of Contents:** 11 11 12 12 {{toc/}} ... ... @@ -15,59 +15,64 @@ 15 15 16 16 17 17 16 + 18 18 = 1. Introduction = 19 19 19 +== 1.1 What is NDDS75 Distance Detection Sensor == 20 20 21 -== 1.1 What is N95S31B NB-IoT Sensor Node == 22 - 23 23 ((( 24 24 25 25 26 26 ((( 27 -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*. 25 +((( 26 +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. 28 28 ))) 29 29 30 30 ((( 31 -The temperature& humiditysensor usedinN95S31BisSHT31,whichisfullycalibrated,linearized,and temperature compensateddigitaloutputfromSensirion,itprovidesastrongreliabilityandlong-termstability.TheSHT31isfixedina(%style="color:blue"%)**waterproofanti-condensationcasing**(%%)forongtermuse.30 +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. 32 32 ))) 33 33 34 34 ((( 35 -N 95S31B supportsdifferentuplinkmethodsinclude (%style="color:blue"%)**TCP,MQTT,UDPandCoAP**(%%)fordifferentapplication requirement.34 +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. 36 36 ))) 37 37 38 38 ((( 39 -N 95S31Bisweredby(% style="color:blue" %)**8500mAh Li-SOCI2battery**(%%),Itis designedforlong term use up to several years.(Real-worldbattery lifedepends on the use environment,updateperiod. Pleasecheck related Power Analyzereport).38 +NDDS75 supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP and CoAP** (%%)for different application requirement. 40 40 ))) 41 41 42 42 ((( 43 - 42 +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) 44 44 ))) 45 45 46 46 ((( 47 - ~*makesureyouhave NB-IoT coverage locally.46 +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. 48 48 ))) 48 +))) 49 49 50 50 51 51 ))) 52 52 53 -[[image:16573 48284168-431.png]]53 +[[image:1657327959271-447.png]] 54 54 55 55 56 56 57 57 == 1.2 Features == 58 58 59 - 60 60 * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD 61 -* Monitor Temperature & Humidity via SHT31 60 +* Ultra low power consumption 61 +* Distance Detection by Ultrasonic technology 62 +* Flat object range 280mm - 7500mm 63 +* Accuracy: ±(1cm+S*0.3%) (S: Distance) 64 +* Cable Length: 25cm 62 62 * AT Commands to change parameters 63 63 * Uplink on periodically 64 64 * Downlink to change configure 65 65 * IP66 Waterproof Enclosure 66 -* Ultra-Low Power consumption 67 -* AT Commands to change parameters 68 68 * Micro SIM card slot for NB-IoT SIM 69 69 * 8500mAh Battery for long term use 70 70 72 + 73 + 71 71 == 1.3 Specification == 72 72 73 73 ... ... @@ -93,9 +93,15 @@ 93 93 * Max continuously current: 130mA 94 94 * Max boost current: 2A, 1 second 95 95 96 - ==1.4Applications ==99 +(% style="color:#037691" %)**Power Consumption** 97 97 101 +* STOP Mode: 10uA @ 3.3v 102 +* Max transmit power: 350mA@3.3v 98 98 104 + 105 + 106 +== 1.4 Applications == 107 + 99 99 * Smart Buildings & Home Automation 100 100 * Logistics and Supply Chain Management 101 101 * Smart Metering ... ... @@ -107,68 +107,24 @@ 107 107 108 108 109 109 119 +== 1.5 Pin Definitions == 110 110 111 -== 1.5 Pin Definitions & Switch == 112 112 122 +[[image:1657328609906-564.png]] 113 113 114 -N95S31B use the mother board from NBSN95 which as below. 115 115 116 116 117 - [[image:image-20220709144723-1.png]]126 += 2. Use NDDS75 to communicate with IoT Server = 118 118 119 - 120 - 121 -=== 1.5.1 Jumper JP2 === 122 - 123 - 124 -Power on Device when put this jumper. 125 - 126 - 127 - 128 -=== 1.5.2 BOOT MODE / SW1 === 129 - 130 - 131 -((( 132 -**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. 133 -))) 134 - 135 -((( 136 -**2) Flash:** work mode, device starts to work and send out console output for further debug 137 -))) 138 - 139 - 140 - 141 -=== 1.5.3 Reset Button === 142 - 143 - 144 -Press to reboot the device. 145 - 146 - 147 - 148 -=== 1.5.4 LED === 149 - 150 - 151 -It will flash: 152 - 153 -1. When boot the device in flash mode 154 - 155 -2. Send an uplink packet 156 - 157 - 158 - 159 -= 2. Use N95S31B to communicate with IoT Server = 160 - 161 - 162 162 == 2.1 How it works == 163 163 164 - 165 165 ((( 166 -The N 95S31Bis equipped with a NB-IoT module, the pre-loaded firmware in N95S31Bwill 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.131 +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. 167 167 ))) 168 168 169 169 170 170 ((( 171 -The diagram below shows the working flow in default firmware of N 95S31B:136 +The diagram below shows the working flow in default firmware of NDDS75: 172 172 ))) 173 173 174 174 ((( ... ... @@ -175,7 +175,7 @@ 175 175 176 176 ))) 177 177 178 -[[image:1657 520100595-569.png]]143 +[[image:1657328659945-416.png]] 179 179 180 180 ((( 181 181 ... ... @@ -182,69 +182,30 @@ 182 182 ))) 183 183 184 184 185 -== 2.2 Configure the N 95S31B==150 +== 2.2 Configure the NDDS75 == 186 186 187 187 188 -=== 2.2.1 Power On N95S31B === 189 - 190 - 191 -[[image:image-20220709150546-2.png]] 192 - 193 - 194 - 195 195 === 2.2.1 Test Requirement === 196 196 197 - 198 198 ((( 199 -To use N 95S31Bin your city, make sure meet below requirements:156 +To use NDDS75 in your city, make sure meet below requirements: 200 200 ))) 201 201 202 -* ((( 203 -Your local operator has already distributed a NB-IoT Network there. 204 -))) 205 -* ((( 206 -The local NB-IoT network used the band that N95S31B supports. 207 -))) 208 -* ((( 209 -Your operator is able to distribute the data received in their NB-IoT network to your IoT server. 210 -))) 159 +* Your local operator has already distributed a NB-IoT Network there. 160 +* The local NB-IoT network used the band that NSE01 supports. 161 +* Your operator is able to distribute the data received in their NB-IoT network to your IoT server. 211 211 212 212 ((( 213 -Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8. 164 +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 214 214 ))) 215 215 216 -((( 217 -N95S31B supports different communication protocol such as : 218 -))) 219 219 220 -((( 221 -* ((( 222 -CoAP ((% style="color:red" %)120.24.4.116:5683(%%)) 223 -))) 224 -* ((( 225 -raw UDP ((% style="color:red" %)120.24.4.116:5601(%%)) 226 -))) 227 -* ((( 228 -MQTT ((% style="color:red" %)120.24.4.116:1883(%%)) 229 -))) 230 -* ((( 231 -TCP ((% style="color:red" %)120.24.4.116:5600(%%)) 232 -))) 168 +[[image:1657328756309-230.png]] 233 233 234 -((( 235 -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. 236 -))) 237 237 238 - 239 -))) 240 240 241 - [[image:1657350625843-586.png]]172 +=== 2.2.2 Insert SIM card === 242 242 243 - 244 - 245 -=== 2.2.3 Insert SIM card === 246 - 247 - 248 248 ((( 249 249 Insert the NB-IoT Card get from your provider. 250 250 ))) ... ... @@ -254,33 +254,29 @@ 254 254 ))) 255 255 256 256 257 -[[image:16573 51240556-536.png]]183 +[[image:1657328884227-504.png]] 258 258 259 259 260 260 261 -=== 2.2. 4Connect USB – TTL to N95S31Bto configure it ===187 +=== 2.2.3 Connect USB – TTL to NDDS75 to configure it === 262 262 263 - 264 264 ((( 265 265 ((( 266 -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. 267 - 268 - 191 +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. 269 269 ))) 270 270 ))) 271 271 272 -[[image: 1657351312545-300.png]]195 +[[image:image-20220709092052-2.png]] 273 273 197 +**Connection:** 274 274 275 -(% style="color: blue" %)**Connection:**199 + (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND 276 276 277 - (% style="background-color:yellow" %) **USB TTLGND <~-~-~-~->GND**201 + (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD 278 278 279 - **~(% style="background-color:yellow" %)USB TTLTXD <~-~-~-~-> UART_RXD(%%)**203 + (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD 280 280 281 -**~ (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD(%%)** 282 282 283 - 284 284 In the PC, use below serial tool settings: 285 285 286 286 * Baud: (% style="color:green" %)**9600** ... ... @@ -290,24 +290,22 @@ 290 290 * Flow Control: (% style="color:green" %)**None** 291 291 292 292 ((( 293 -Make sure the switch is in FLASH position, then power on device by connecting the jumper on N 95S31B.95S31Bwill output system info once power on as below, we can enter the (% style="color:green" %)**password: 12345678**(%%) to access AT Command input.215 +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. 294 294 ))) 295 295 296 296 [[image:1657329814315-101.png]] 297 297 298 - 299 299 ((( 300 -(% 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]]**221 +(% 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/]] 301 301 ))) 302 302 303 303 304 304 305 -=== 2.2. 5Use CoAP protocol to uplink data ===226 +=== 2.2.4 Use CoAP protocol to uplink data === 306 306 228 +(% 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/]] 307 307 308 -(% 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/]]** 309 309 310 - 311 311 ((( 312 312 **Use below commands:** 313 313 ))) ... ... @@ -316,19 +316,17 @@ 316 316 (% style="color:blue" %)**AT+PRO=1** (%%) ~/~/ Set to use CoAP protocol to uplink 317 317 ))) 318 318 * ((( 319 -(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683 ** 239 +(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683 ** (%%)~/~/ to set CoAP server address and port 320 320 ))) 321 321 * ((( 322 -(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/ 242 +(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path 323 323 ))) 324 324 325 325 ((( 326 - 327 - 328 328 For parameter description, please refer to AT command set 329 329 ))) 330 330 331 -[[image:1657352 146020-183.png]]249 +[[image:1657330452568-615.png]] 332 332 333 333 334 334 ((( ... ... @@ -335,11 +335,11 @@ 335 335 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. 336 336 ))) 337 337 338 -[[image:16573 52185396-303.png]]256 +[[image:1657330472797-498.png]] 339 339 340 340 341 341 342 -=== 2.2. 6Use UDP protocol to uplink data(Default protocol) ===260 +=== 2.2.5 Use UDP protocol to uplink data(Default protocol) === 343 343 344 344 345 345 * (% style="color:blue" %)**AT+PRO=2 ** (%%) ~/~/ Set to use UDP protocol to uplink ... ... @@ -346,119 +346,109 @@ 346 346 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601 ** (%%) ~/~/ to set UDP server address and port 347 347 * (% style="color:blue" %)**AT+CFM=1 ** (%%) ~/~/ If the server does not respond, this command is unnecessary 348 348 349 -[[image:16573 52391268-297.png]]267 +[[image:1657330501006-241.png]] 350 350 351 351 352 -[[image:16573 52403317-397.png]]270 +[[image:1657330533775-472.png]] 353 353 354 354 355 355 356 -=== 2.2. 7Use MQTT protocol to uplink data ===274 +=== 2.2.6 Use MQTT protocol to uplink data === 357 357 358 358 359 -N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption. 277 +* (% style="color:blue" %)**AT+PRO=3 ** (%%) ~/~/Set to use MQTT protocol to uplink 278 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) ~/~/Set MQTT server address and port 279 +* (% style="color:blue" %)**AT+CLIENT=CLIENT ** (%%)~/~/Set up the CLIENT of MQTT 280 +* (% style="color:blue" %)**AT+UNAME=UNAME **(%%)~/~/Set the username of MQTT 281 +* (% style="color:blue" %)**AT+PWD=PWD **(%%)~/~/Set the password of MQTT 282 +* (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB **(%%)~/~/Set the sending topic of MQTT 283 +* (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB **(%%) ~/~/Set the subscription topic of MQTT 360 360 361 -* (% style="color:blue" %)**AT+PRO=3 ** (%%) ~/~/ Set to use MQTT protocol to uplink 362 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) ~/~/ Set MQTT server address and port 363 -* (% style="color:blue" %)**AT+CLIENT=CLIENT ** (%%)~/~/ Set up the CLIENT of MQTT 364 -* (% style="color:blue" %)**AT+UNAME=UNAME **(%%)~/~/ Set the username of MQTT 365 -* (% style="color:blue" %)**AT+PWD=PWD **(%%)~/~/ Set the password of MQTT 366 -* (% style="color:blue" %)**AT+PUBTOPIC=f9527 **(%%)~/~/ Set the sending topic of MQTT 367 -* (% style="color:blue" %)**AT+SUBTOPIC=Ns9527 **(%%) ~/~/ Set the subscription topic of MQTT 285 +[[image:1657249978444-674.png]] 368 368 369 -[[image:1657352634421-276.png]] 370 370 288 +[[image:1657330723006-866.png]] 371 371 372 -[[image:1657352645687-385.png]] 373 373 374 - 375 375 ((( 376 -To savebatterylife,N95S31Bwillestablishasubscriptionbeforeeachuplinkandclose thesubscription3 secondsafteruplinksuccessful. Any downlink commandsfromserver will onlyarriveduringthesubscriptionperiod.292 +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. 377 377 ))) 378 378 379 379 380 -((( 381 -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. 382 -))) 383 383 297 +=== 2.2.7 Use TCP protocol to uplink data === 384 384 385 385 386 -=== 2.2.8 Use TCP protocol to uplink data === 387 - 388 - 389 -This feature is supported since firmware version v110 390 - 391 391 * (% style="color:blue" %)**AT+PRO=4 ** (%%) ~/~/ Set to use TCP protocol to uplink 392 392 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600 **(%%) ~/~/ to set TCP server address and port 393 393 394 -[[image: 1657352898400-901.png]]303 +[[image:image-20220709093918-1.png]] 395 395 396 396 397 -[[image: 1657352914475-252.png]]306 +[[image:image-20220709093918-2.png]] 398 398 399 399 400 400 401 -=== 2.2. 9Change Update Interval ===310 +=== 2.2.8 Change Update Interval === 402 402 403 - 404 404 User can use below command to change the (% style="color:green" %)**uplink interval**. 405 405 406 406 * (% style="color:blue" %)**AT+TDC=600 ** (%%)~/~/ Set Update Interval to 600s 407 407 408 408 ((( 409 - 317 +(% style="color:red" %)**NOTE:** 410 410 ))) 411 411 412 412 ((( 413 -(% style="color:red" %) **NOTE:Sincefirmware version is v1.2:**321 +(% style="color:red" %)1. By default, the device will send an uplink message every 1 hour. 414 414 ))) 415 415 416 -((( 417 -(% style="color:red" %)**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).** 418 -))) 419 419 420 420 421 - 422 422 == 2.3 Uplink Payload == 423 423 328 +In this mode, uplink payload includes in total 14 bytes 424 424 425 -((( 426 -N95S31B has different working modes for the connections of different types 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. 427 -))) 428 428 331 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %) 332 +|=(% style="width: 60px;" %)((( 333 +**Size(bytes)** 334 +)))|=(% style="width: 60px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 80px;" %)**1**|=(% style="width: 100px;" %)**2**|=(% style="width: 60px;" %)**1** 335 +|(% 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"]] 429 429 430 430 ((( 431 - For example:338 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS751 uplink data. 432 432 ))) 433 433 434 -((( 435 - (% 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. 436 -))) 437 437 342 +[[image:1657331036973-987.png]] 438 438 439 439 ((( 440 -The uplink payloadsare composedinASCIIString.Forxample:345 +The payload is ASCII string, representative same HEX: 441 441 ))) 442 442 443 443 ((( 444 -0 a cd00ed0acc0ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload:349 +0x72403155615900640c6c19029200 where: 445 445 ))) 446 446 447 -((( 448 - 0x 0acd 00ed0acc0000ef 02d21d Total12 bytes352 +* ((( 353 +Device ID: 0x724031556159 = 724031556159 449 449 ))) 450 - 451 - 452 -((( 453 -(% style="color:red" %)**NOTE:** 355 +* ((( 356 +Version: 0x0064=100=1.0.0 454 454 ))) 455 455 456 -(% style="color:red" %) 457 -1. ((( 458 -**All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]].** 359 +* ((( 360 +BAT: 0x0c6c = 3180 mV = 3.180V 459 459 ))) 460 -1. ((( 461 -**By default, the device will send an uplink message every 1 hour.** 362 +* ((( 363 +Signal: 0x19 = 25 364 +))) 365 +* ((( 366 +Distance: 0x0292= 658 mm 367 +))) 368 +* ((( 369 +Interrupt: 0x00 = 0 462 462 463 463 464 464 ... ... @@ -465,188 +465,105 @@ 465 465 466 466 ))) 467 467 468 -== =2.3.1PayloadAnalyze ===376 +== 2.4 Payload Explanation and Sensor Interface == 469 469 470 470 471 -=== =2.3.1.1Before Firmwarev1.2====379 +=== 2.4.1 Device ID === 472 472 473 - 474 -N95S31B uplink payload includes in total 21 bytes 475 - 476 - 477 -(% border="1" style="background-color:#ffffcc; color:green; width:520px" %) 478 -|=(% scope="row" style="width: 50px;" %)**Size(bytes)**|=(% style="width: 40px;" %)**6**|=(% style="width: 20px;" %)2|=(% style="width: 20px;" %)**2**|=(% style="width: 60px;" %)**1**|=(% style="width: 50px;" %)1|=(% style="width: 100px;" %)5|=(% style="width: 50px;" %)**2**|=(% style="width: 50px;" %)**2** 479 -|(% style="width:97px" %)**Value**|(% style="width:65px" %)[[Device ID>>||anchor="H2.3.2A0DeviceID"]]|(% style="width:50px" %)[[Ver>>||anchor="H2.3.3A0VersionInfo"]]|(% style="width:46px" %)[[BAT>>||anchor="H2.3.4A0BatteryInfo"]]|(% style="width:75px" %)[[Signal Strength>>||anchor="H2.3.5A0SignalStrength"]]|(% style="width:59px" %)MOD 0X01|(% style="width:162px" %)((( 480 480 ((( 481 - Reserve/Same asNBSN95CFGMOD=1382 +By default, the Device ID equal to the last 6 bytes of IMEI. 482 482 ))) 483 483 484 484 ((( 485 - Nofunctionhere.386 +User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID 486 486 ))) 487 -)))|(% style="width:102px" %)((( 488 -((( 489 -[[Temperature >>||anchor="H2.3.6A0Temperature26Humidity"]] 490 -))) 491 491 492 492 ((( 493 - By SHT31390 +**Example:** 494 494 ))) 495 -)))|(% style="width:81px" %)((( 496 -((( 497 -[[Humidity>>||anchor="H2.3.6A0Temperature26Humidity"]] 498 -))) 499 499 500 500 ((( 501 - By SHT31394 +AT+DEUI=A84041F15612 502 502 ))) 503 -))) 504 504 505 505 ((( 506 - 507 - 508 -((( 509 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data. 398 +The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID. 510 510 ))) 511 -))) 512 512 513 513 514 -[[image:1657354294009-643.png]] 515 515 403 +=== 2.4.2 Version Info === 516 516 517 -The payload is ASCII string, representative same HEX: (% style="background-color:yellow" %)**0x724031607457 006e 0ccd 1b 01 00dc000ccc 00e1 0186** 405 +((( 406 +Specify the software version: 0x64=100, means firmware version 1.00. 407 +))) 518 518 519 -**where:** 409 +((( 410 +For example: 0x00 64 : this device is NDDS75 with firmware version 1.0.0. 411 +))) 520 520 521 -* (% style="color:#037691" %)**Device ID:** (%%) 0x724031607457 = 724031607457 522 522 523 -* (% style="color:#037691" %)**Version: **(%%) 0x006e=110=1.1.0 524 524 525 - *(%style="color:#037691"%)**BAT:**(%%) 0x0ccd=3277 mV=3.277V415 +=== 2.4.3 Battery Info === 526 526 527 -* (% style="color:#037691" %)**Signal:** (%%) 0x1b = 27 528 - 529 -* (% style="color:#037691" %)**Model:** (%%) 0x01 = 1 530 - 531 -* (% style="color:#037691" %)**0x00dc000ccc= reserve, ignore in N95S31B** 532 - 533 -* (% style="color:#037691" %)**Temperature by SHT31:** (%%) 0x00e1 = 225 = 22.5 °C 534 - 535 -* (% style="color:#037691" %)**Humidity by SHT31:** (%%) 0x0186 = 390 = 39.0 %rh 536 - 537 537 ((( 538 - 418 +Ex1: 0x0B45 = 2885mV 419 +))) 539 539 540 - 541 - 421 +((( 422 +Ex2: 0x0B49 = 2889mV 542 542 ))) 543 543 544 -==== 2.3.1.2 Since Firmware v1.2 ==== 545 545 546 546 547 - Inthismode, uplink payloadincludes 91 bytes inotalby default.427 +=== 2.4.4 Signal Strength === 548 548 549 -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. 550 - 551 - 552 -(% border="1" style="background-color:#ffffcc; color:green; width:520px" %) 553 -|=(% scope="row" style="width: 50px;" %)**Size(bytes)**|(% style="width:40px" %)**8**|(% style="width:25px" %)**2**|(% style="width:25px" %)**2**|(% style="width:30px" %)**1**|(% style="width:25px" %)**1**|(% style="width:40px" %)**2**|(% style="width:30px" %)**1**|(% style="width:25px" %)**2**|(% style="width:30px" %)**2**|(% style="width:30px" %)**2**|(% style="width:30px" %)**4**|(% style="width:30px" %)**2**|(% style="width:30px" %)**2**|(% style="width:30px" %)**4** 554 -|=(% style="width: 95px;" %)**Value**|(% style="width:82px" %)Device ID|(% style="width:43px" %)Ver|(% style="width:47px" %)BAT|(% style="width:124px" %)Signal Strength|(% style="width:56px" %)MOD|(% style="width:109px" %)TemDS18B20|(% style="width:80px" %)Interrupt|(% style="width:51px" %)ADC|(% style="width:79px" %)SHTTEM|(% style="width:84px" %)SHTHUM|(% style="width:100px" %)Time stamp |(% style="width:76px" %)SHTTEM|(% style="width:81px" %)SHTHUM|(% style="width:121px" %)Time stamp ..... 555 - 556 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the N95S31B uplink data. 557 - 558 - 559 -[[image:image-20220908154949-1.png]] 560 - 561 - 562 -The payload is ASCII string, representative same HEX: 563 - 564 -**0x (% style="color:red" %)__f868411056758782__ (% style="color:blue" %)__000c__ (% style="color:green" %)__0d0f__ (% style="color:#00b0f0" %)__0c__ (% style="color:#7030a0" %)__01__ (% style="color:#d60093" %)__0000__ (% style="color:#a14d07" %)__00__ __0030__ (% style="color:#0020b0" %)__0114__ (% style="color:#420042" %)__0231__ (% style="color:#663300" %)__63199d3c__ (%%)__0113023163199d12__ __0113023163199c5e__// //__0112023763199baa__ __0112023263199af6__// //__0111023b631999a7__ ** 565 - 566 -**__0112023b631998f3__// //__011202426319983f__ __01110242631996eb__** 567 - 568 -**where:** 569 - 570 -* (% style="color:#037691" %)**Device ID:**(%%) f868411056758782 = f868411056758782 571 - 572 -* (% style="color:#037691" %)**Version:** (%%)0x000c=120=1.2 573 - 574 -* (% style="color:#037691" %)**BAT:** (%%)0x0d0f = 3343 mV = 3.343V 575 - 576 -* (% style="color:#037691" %)**Singal:**(%%) 0x0c = 12 577 - 578 -* (% style="color:#037691" %)**Mod:**(%%) 0x01 = 1 579 - 580 -* (% style="color:#037691" %)**TemDS18B20:**(%%) 0x0000= 0 = 0 581 - 582 -* (% style="color:#037691" %)**Interrupt:** (%%)0x00= 0 583 - 584 -* (% style="color:#037691" %)**adc:**(%%) 0x0030= 48 585 - 586 -* (% style="color:#037691" %)**SHTTEM:**(%%) 0x0114= 276 = 27.6 587 - 588 -* (% style="color:#037691" %)**SHTHUM:**(%%) 0x0231 =561=56.1% 589 - 590 -* (% style="color:#037691" %)**Time stamp : **(%%)0x63199d3c =1662342011 ([[Unix Epoch Time>>url:http://www.epochconverter.com/]]) 591 - 592 -* (% style="color:#037691" %)**SHTTEM,SHTHUM,Time stamp :**(%%) 0113023163199d12 593 - 594 -* (% style="color:#037691" %)**8 sets of recorded data:**(%%)** **SHTTEM,SHTHUM,Time stamp : 0113023163199c5e, ....... 595 - 596 -=== 2.3.2 Device ID === 597 - 598 - 599 599 ((( 600 -B ydefault,the Device ID equal to thelast6 bytes of IMEI.430 +NB-IoT Network signal Strength. 601 601 ))) 602 602 603 603 ((( 604 -User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID 434 +**Ex1: 0x1d = 29** 435 +))) 605 605 606 - 437 +((( 438 +(% style="color:blue" %)**0**(%%) -113dBm or less 607 607 ))) 608 608 609 609 ((( 610 -(% style="color:blue" %)** Example:**442 +(% style="color:blue" %)**1**(%%) -111dBm 611 611 ))) 612 612 613 613 ((( 614 - AT+DEUI=A84041F15612446 +(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm 615 615 ))) 616 616 617 617 ((( 618 -The Device ID is stored in a none-erase area, Upgrade the firmware or run (% style="color:blue" %)**AT+FDR**(%%) won't erase Device ID. 450 +(% style="color:blue" %)**31** (%%) -51dBm or greater 451 +))) 619 619 620 - 453 +((( 454 +(% style="color:blue" %)**99** (%%) Not known or not detectable 621 621 ))) 622 622 623 -(% style="color:red" %)**NOTE: When the firmware version is v1.2 and later firmware:** 624 624 625 625 626 - Bydefault,theDeviceID equal to the last 15 bits of IMEI.459 +=== 2.4.5 Distance === 627 627 628 - Usercan use**(%style="color:blue"%)AT+DEUI(%%)**tosetDeviceID461 +Get the distance. Flat object range 280mm - 7500mm. 629 629 630 - 631 -(% style="color:blue" %)**Example:** 632 - 633 -AT+DEUI=868411056754138 634 - 635 - 636 - 637 -=== 2.3.3 Version Info === 638 - 639 - 640 640 ((( 641 - Thesebytes include the hardware andsoftwareversion.464 +For example, if the data you get from the register is **__0x0B 0x05__**, the distance between the sensor and the measured object is 642 642 ))) 643 643 644 644 ((( 645 -Higher byte: Specify hardware version: always 0x00 for N95S31B 468 +((( 469 +(% style="color:blue" %)** 0B05(H) = 2821(D) = 2821mm.** 646 646 ))) 471 +))) 647 647 648 648 ((( 649 - Lowerbyte: Specify the software version: 0x6E=110, means firmware version 110474 + 650 650 ))) 651 651 652 652 ((( ... ... @@ -653,85 +653,65 @@ 653 653 654 654 ))) 655 655 481 +=== 2.4.6 Digital Interrupt === 482 + 656 656 ((( 657 - For example:0x00 6E:thisdevice isN95S31Bwithfirmwareversion110.484 +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. 658 658 ))) 659 659 660 660 ((( 661 - 488 +The command is: 662 662 ))) 663 663 664 - 665 -=== 2.3.4 Battery Info === 666 - 667 - 668 668 ((( 669 - Ex1:0x0B45=2885mV492 +(% 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]])**.** 670 670 ))) 671 671 495 + 672 672 ((( 673 - Ex2:0x0B49=2889mV497 +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. 674 674 ))) 675 675 676 676 677 - 678 -=== 2.3.5 Signal Strength === 679 - 680 - 681 681 ((( 682 - NB-IoT Network signalStrength.502 +Example: 683 683 ))) 684 684 685 685 ((( 686 - **Ex1:0x1d=29**506 +0x(00): Normal uplink packet. 687 687 ))) 688 688 689 689 ((( 690 -( %style="color:blue"%)**0**(%%) -113dBm orless510 +0x(01): Interrupt Uplink Packet. 691 691 ))) 692 692 513 + 514 + 515 +=== 2.4.7 +5V Output === 516 + 693 693 ((( 694 - (%style="color:blue"%)**1**(%%)-111dBm518 +NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling. 695 695 ))) 696 696 521 + 697 697 ((( 698 - (%style="color:blue"%)**2...30**(%%)-109dBm...-53dBm523 +The 5V output time can be controlled by AT Command. 699 699 ))) 700 700 701 701 ((( 702 -(% style="color:blue" %)** 31**(%%) -51dBm or greater527 +(% style="color:blue" %)**AT+5VT=1000** 703 703 ))) 704 704 705 705 ((( 706 - (%style="color:blue"%)**99**(%%)Notknownornotdetectable531 +Means set 5V valid time to have 1000ms. So the real 5V output will actually have 1000ms + sampling time for other sensors. 707 707 ))) 708 708 709 709 710 710 711 -== =2.3.6Temperature & Humidity ===536 +== 2.5 Downlink Payload == 712 712 538 +By default, NDDS75 prints the downlink payload to console port. 713 713 714 -The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server. 715 - 716 -[[image:image-20220709161741-3.png]] 717 - 718 - 719 -Convert the read byte to decimal and divide it by ten. 720 - 721 - 722 -**Example:** 723 - 724 -Temperature: Read:00ec (H) = 236(D) Value: 236 /10=23.6℃ 725 - 726 -Humidity: Read:0295(H)=661(D) Value: 661 / 10=66.1, So 66.1% 727 - 728 - 729 - 730 -== 2.4 Downlink Payload == 731 - 732 - 733 -By default, N95S31B prints the downlink payload to console port. 734 - 735 735 [[image:image-20220709100028-1.png]] 736 736 737 737 ... ... @@ -768,7 +768,7 @@ 768 768 ))) 769 769 770 770 ((( 771 -If payload = 0x04FF, it will reset the 95S31B576 +If payload = 0x04FF, it will reset the NDDS75 772 772 ))) 773 773 774 774 ... ... @@ -780,76 +780,48 @@ 780 780 781 781 782 782 783 -== 2. 5HumidityandTemperaturealarm function==588 +== 2.6 LED Indicator == 784 784 785 785 786 - **~(%style="color:blue"%)➢ATCommand:(%%)**591 +The NDDS75 has an internal LED which is to show the status of different state. 787 787 788 788 789 -(% style="color:#037691" %)**AT+ SHHUM=min,max** 594 +* When power on, NDDS75 will detect if sensor probe is connected, if probe detected, LED will blink four times. (no blinks in this step is no probe) 595 +* Then the LED will be on for 1 second means device is boot normally. 596 +* After NDDS75 join NB-IoT network. The LED will be ON for 3 seconds. 597 +* For each uplink probe, LED will be on for 500ms. 790 790 599 +((( 600 + 601 +))) 791 791 792 -² When min=0, and max≠0, Alarm higher than max 793 793 794 -² When min≠0, and max=0, Alarm lower than min 795 795 796 - ²Whenmin≠0 andmax≠0, Alarm higherthanmaxorlower than min605 +== 2.7 Firmware Change Log == 797 797 798 798 799 - (% style="color:blue" %)**Example:** 608 +((( 609 +Download URL & Firmware Change log 610 +))) 800 800 801 -AT+ SHHUM=50,80 ~/~/ Alarm when humidity lower than 50. 612 +((( 613 +[[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/]] 614 +))) 802 802 803 803 804 -(% style="color:#037691" %)**AT+ SHTEMP=min,max** 617 +((( 618 +Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]] 619 +))) 805 805 806 -² When min=0, and max≠0, Alarm higher than max 807 807 808 -² When min≠0, and max=0, Alarm lower than min 809 809 810 -² When min≠0 and max≠0, Alarm higher than max or lower than min 811 - 812 - 813 -**~ (% style="color:blue" %)Example:(%%)** 814 - 815 -AT+ SHTEMP=20,30 ~/~/ Alarm when temperature lower than 20. 816 - 817 - 818 - 819 -== 2.6 Set the number of data to be uploaded and the recording time == 820 - 821 - 822 -**~ (% style="color:blue" %)➢ AT Command:(%%)** 823 - 824 -* (% style="color:#037691" %)**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) 825 -* (% style="color:#037691" %)**AT+NOUD=8** (%%)~/~/ The device uploads 8 sets of recorded data by default. Up to 32 sets of record data can be uploaded. 826 - 827 - The diagram below explains the relationship between TR, NOUD, and TDC more clearly**:** 828 - 829 -[[image:image-20221009001045-1.png||height="726" width="1009"]] 830 - 831 - 832 - 833 -== 2.7 Read or Clear cached data == 834 - 835 - 836 -**~ (% style="color:blue" %)➢ AT Command:(%%)** 837 - 838 -* (% style="color:#037691" %)**AT+CDP** (%%) ~/~/ Read cached data 839 -* (% style="color:#037691" %)**AT+CDP=0** (%%) ~/~/ Clear cached data 840 - 841 -[[image:image-20220908163102-2.png]] 842 - 843 - 844 - 845 845 == 2.8 Battery Analysis == 846 846 847 - 848 848 === 2.8.1 Battery Type === 849 849 850 850 851 851 ((( 852 -The N 95S31Bbattery 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.629 +The NDDS75 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. 853 853 ))) 854 854 855 855 ((( ... ... @@ -872,35 +872,54 @@ 872 872 873 873 === 2.8.2 Power consumption Analyze === 874 874 652 +((( 653 +Dragino battery powered product are all runs in Low Power mode. We have an update battery calculator which base on the measurement of the real device. User can use this calculator to check the battery life and calculate the battery life if want to use different transmit interval. 654 +))) 875 875 656 + 876 876 ((( 877 - 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 toanalyzethe powerconsumption in different case.User can useit for design guideline for their project.658 +Instruction to use as below: 878 878 ))) 879 879 880 880 ((( 881 - 662 +(% style="color:blue" %)**Step 1: **(%%)Downlink the up-to-date DRAGINO_Battery_Life_Prediction_Table.xlsx from: [[https:~~/~~/www.dragino.com/downloads/index.php?dir=LoRa_End_Node/Battery_Analyze/>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_End_Node/Battery_Analyze/]] 882 882 ))) 883 883 884 884 885 -=== 2.8.3 Battery Note === 666 +((( 667 +(% style="color:blue" %)**Step 2: **(%%) Open it and choose 668 +))) 886 886 670 +* ((( 671 +Product Model 672 +))) 673 +* ((( 674 +Uplink Interval 675 +))) 676 +* ((( 677 +Working Mode 678 +))) 887 887 888 888 ((( 889 - The Li-SICO batteryis designed for smallcurrent/ long periodapplication.Itisnotgoodto use a high current, short period transmit method. The recommendedminimum period for useof thisbatteryis5 minutes. If you use a shorterperiod time to uplinkdata, thenthe battery life may be decreased.681 +And the Life expectation in difference case will be shown on the right. 890 890 ))) 891 891 684 +[[image:image-20220709110451-3.png]] 892 892 893 893 894 -=== 2.8.4 Replace the battery === 895 895 688 +=== 2.8.3 Battery Note === 896 896 897 897 ((( 898 - You can changethebattery intheN95S31B.Thetype ofbatteryis notlimitedaslongas theutput isbetween3vto3.6v.Onthemainboard,there isa diode(D1)betweenthebatteryandthemaincircuit. If youneed touse abatterywith less than 3.3v,pleaseremove the D1 andshortcut the twopadsofitso there won'tbe voltagedropbetween batteryandmainboard.691 +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 transmit LoRa, then the battery life may be decreased. 899 899 ))) 900 900 901 901 695 + 696 +=== 2.8.4 Replace the battery === 697 + 902 902 ((( 903 -The default battery pack of N 95S31Bincludes a ER26500 plus super capacitor. If user can't find this pack locally, they can find ER26500 or equivalence without the SPC1520 capacitor, which will also work in most case. The SPC can enlarge the battery life for high frequency use (update period below 5 minutes).699 +The default battery pack of NDDS75 includes a ER26500 plus super capacitor. If user can't find this pack locally, they can find ER26500 or equivalence without the SPC1520 capacitor, which will also work in most case. The SPC can enlarge the battery life for high frequency use (update period below 5 minutes). 904 904 ))) 905 905 906 906 ... ... @@ -907,7 +907,6 @@ 907 907 908 908 = 3. Access NB-IoT Module = 909 909 910 - 911 911 ((( 912 912 Users can directly access the AT command set of the NB-IoT module. 913 913 ))) ... ... @@ -914,8 +914,6 @@ 914 914 915 915 ((( 916 916 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/]] 917 - 918 - 919 919 ))) 920 920 921 921 [[image:1657333200519-600.png]] ... ... @@ -924,13 +924,11 @@ 924 924 925 925 = 4. Using the AT Commands = 926 926 927 - 928 928 == 4.1 Access AT Commands == 929 929 722 +See this link for detail: [[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/>>url:http://www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN50/]] 930 930 931 -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]] 932 932 933 - 934 934 AT+<CMD>? : Help on <CMD> 935 935 936 936 AT+<CMD> : Run <CMD> ... ... @@ -970,24 +970,7 @@ 970 970 971 971 AT+SERVADDR : Server Address 972 972 973 -AT+TR : Get or Set record time 974 974 975 -AT+APN : Get or set the APN 976 - 977 -AT+FBAND : Get or Set whether to automatically modify the frequency band 978 - 979 -AT+DNSCFG : Get or Set DNS Server 980 - 981 -AT+GETSENSORVALUE : Returns the current sensor measurement 982 - 983 -AT+NOUD : Get or Set the number of data to be uploaded 984 - 985 -AT+CDP : Read or Clear cached data 986 - 987 -AT+SHTEMP: Get or Set alarm of temp 988 - 989 -AT+SHHUM: Get or Set alarm of moisture 990 - 991 991 (% style="color:#037691" %)**COAP Management** 992 992 993 993 AT+URI : Resource parameters ... ... @@ -1021,7 +1021,6 @@ 1021 1021 1022 1022 = 5. FAQ = 1023 1023 1024 - 1025 1025 == 5.1 How to Upgrade Firmware == 1026 1026 1027 1027 ... ... @@ -1034,18 +1034,13 @@ 1034 1034 ))) 1035 1035 1036 1036 ((( 1037 - 1038 - 1039 -((( 1040 -(% style="color:red" %)**Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update.** 810 +(% style="color:red" %)Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update. 1041 1041 ))) 1042 -))) 1043 1043 1044 1044 1045 1045 1046 1046 = 6. Trouble Shooting = 1047 1047 1048 - 1049 1049 == 6.1 Connection problem when uploading firmware == 1050 1050 1051 1051 ... ... @@ -1061,7 +1061,6 @@ 1061 1061 1062 1062 == 6.2 AT Command input doesn't work == 1063 1063 1064 - 1065 1065 ((( 1066 1066 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. 1067 1067 ... ... @@ -1072,7 +1072,7 @@ 1072 1072 = 7. Order Info = 1073 1073 1074 1074 1075 -Part Number**:** (% style="color:#4f81bd" %)**N 95S31B-YY**842 +Part Number**:** (% style="color:#4f81bd" %)**NSDDS75** 1076 1076 1077 1077 1078 1078 (% class="wikigeneratedid" %) ... ... @@ -1087,7 +1087,7 @@ 1087 1087 1088 1088 (% style="color:#037691" %)**Package Includes**: 1089 1089 1090 -* N 95S31BNB-IoTTemperatureandHumiditySensor857 +* NSE01 NB-IoT Distance Detect Sensor Node x 1 1091 1091 * External antenna x 1 1092 1092 ))) 1093 1093 ... ... @@ -1096,10 +1096,11 @@ 1096 1096 1097 1097 (% style="color:#037691" %)**Dimension and weight**: 1098 1098 866 + 1099 1099 * Device Size: 13.0 x 5 x 4.5 cm 1100 1100 * Device Weight: 150g 1101 -* Package Size / pcs : 1 4.0x8x 5 cm1102 -* Weight / pcs : 180g869 +* Package Size / pcs : 15 x 12x 5.5 cm 870 +* Weight / pcs : 220g 1103 1103 ))) 1104 1104 1105 1105 ((( ... ... @@ -1111,6 +1111,5 @@ 1111 1111 1112 1112 = 9. Support = 1113 1113 1114 - 1115 1115 * 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. 1116 1116 * 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]]
- 1657348284168-431.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -93.5 KB - Content
- 1657350248151-650.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -126.1 KB - Content
- 1657350625843-586.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -93.3 KB - Content
- 1657351240556-536.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -483.6 KB - Content
- 1657351312545-300.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -675.8 KB - Content
- 1657352146020-183.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -264.0 KB - Content
- 1657352185396-303.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -98.3 KB - Content
- 1657352391268-297.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -238.0 KB - Content
- 1657352403317-397.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -547.7 KB - Content
- 1657352634421-276.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -163.6 KB - Content
- 1657352645687-385.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -214.7 KB - Content
- 1657352898400-901.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -144.8 KB - Content
- 1657352914475-252.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -157.0 KB - Content
- 1657354294009-643.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -214.7 KB - Content
- 1657520100595-569.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -126.1 KB - Content
- image-20220709144723-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -413.1 KB - Content
- image-20220709150546-2.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -333.5 KB - Content
- image-20220709161741-3.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -111.2 KB - Content
- image-20220908154949-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.David - Size
-
... ... @@ -1,1 +1,0 @@ 1 -58.5 KB - Content
- image-20220908163102-2.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.David - Size
-
... ... @@ -1,1 +1,0 @@ 1 -29.7 KB - Content
- image-20221009001045-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Edwin - Size
-
... ... @@ -1,1 +1,0 @@ 1 -282.9 KB - Content