Changes for page NDDS75 -- NB-IoT Distance Detect Sensor User Manual
Last modified by Bei Jinggeng on 2024/05/31 09:53
Summary
-
Page properties (2 modified, 0 added, 0 removed)
-
Attachments (0 modified, 29 added, 0 removed)
- 1657271519014-786.png
- 1657327959271-447.png
- 1657328609906-564.png
- 1657328659945-416.png
- 1657328756309-230.png
- 1657328884227-504.png
- 1657329814315-101.png
- 1657330452568-615.png
- 1657330472797-498.png
- 1657330501006-241.png
- 1657330533775-472.png
- 1657330723006-866.png
- 1657331036973-987.png
- 1657332990863-496.png
- 1657333200519-600.png
- image-20220709084038-1.jpeg
- image-20220709084137-2.jpeg
- image-20220709084207-3.jpeg
- image-20220709084458-4.png
- image-20220709085040-1.png
- image-20220709092052-2.png
- image-20220709093918-1.png
- image-20220709093918-2.png
- image-20220709100028-1.png
- image-20220709101450-2.png
- image-20220709110451-3.png
- image-20220908175246-1.png
- image-20220908175333-2.png
- image-20221009001114-1.png
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -NS E01-NB-IoTSoil Moisture&ECSensor User Manual1 +NDDS75 NB-IoT Distance Detect Sensor User Manual - Content
-
... ... @@ -1,16 +1,10 @@ 1 1 (% style="text-align:center" %) 2 -[[image:image-20220 606151504-2.jpeg||height="554" width="554"]]2 +[[image:image-20220709085040-1.png||height="542" width="524"]] 3 3 4 4 5 5 6 6 7 7 8 - 9 - 10 - 11 - 12 - 13 - 14 14 **Table of Contents:** 15 15 16 16 {{toc/}} ... ... @@ -20,55 +20,62 @@ 20 20 21 21 22 22 23 - 24 24 = 1. Introduction = 25 25 26 -== 1.1 What is LoRaWANoilMoisture&ECSensor ==19 +== 1.1 What is NDDS75 Distance Detection Sensor == 27 27 28 28 ((( 29 29 30 30 31 31 ((( 32 -Dragino NSE01 is an (% style="color:blue" %)**NB-IOT soil moisture & EC sensor**(%%) for agricultural IoT. Used to measure the soil moisture of saline-alkali soil and loam. The soil sensor uses the FDR method to calculate soil moisture and compensates it with soil temperature and electrical conductivity. It has also been calibrated for mineral soil types at the factory. 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. 33 33 ))) 34 34 35 35 ((( 36 - Itcandetect(%style="color:blue"%)**SoilMoisture,SoilTemperature andSoilConductivity**(%%), and uploaditsvalue to the serverwirelessly.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. 37 37 ))) 38 38 39 39 ((( 40 -Th ewirelesstechnologyusedin NSE01 allows theevicetosend dataatalowdatarate andreachultra-longdistances,providingultra-long-distance spread spectrumCommunication.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. 41 41 ))) 42 42 43 43 ((( 44 -NS E01arepoweredby(% style="color:blue" %)**8500mAhLi-SOCI2**(%%)batteries,which canbesed forup to 5 years.38 +NDDS75 supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP and CoAP** (%%)for different application requirement. 45 45 ))) 46 46 47 - 41 +((( 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) 48 48 ))) 49 49 50 -[[image:1654503236291-817.png]] 45 +((( 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. 47 +))) 48 +))) 51 51 50 + 51 +))) 52 52 53 -[[image:16572 45163077-232.png]]53 +[[image:1657327959271-447.png]] 54 54 55 55 56 - 57 57 == 1.2 Features == 58 58 58 + 59 59 * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD 60 -* Monitor Soil Moisture 61 -* Monitor Soil Temperature 62 -* Monitor Soil Conductivity 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 63 63 * AT Commands to change parameters 64 64 * Uplink on periodically 65 65 * Downlink to change configure 66 66 * IP66 Waterproof Enclosure 67 -* Ultra-Low Power consumption 68 -* AT Commands to change parameters 69 69 * Micro SIM card slot for NB-IoT SIM 70 70 * 8500mAh Battery for long term use 71 71 72 + 72 72 == 1.3 Specification == 73 73 74 74 ... ... @@ -79,82 +79,95 @@ 79 79 80 80 (% style="color:#037691" %)**NB-IoT Spec:** 81 81 82 -* -B1 @H-FDD: 2100MHz83 -* -B3 @H-FDD: 1800MHz84 -* -B8 @H-FDD: 900MHz85 -* -B5 @H-FDD: 850MHz86 -* -B20 @H-FDD: 800MHz87 -* -B28 @H-FDD: 700MHz83 +* B1 @H-FDD: 2100MHz 84 +* B3 @H-FDD: 1800MHz 85 +* B8 @H-FDD: 900MHz 86 +* B5 @H-FDD: 850MHz 87 +* B20 @H-FDD: 800MHz 88 +* B28 @H-FDD: 700MHz 88 88 89 - Probe(% style="color:#037691" %)**Specification:**90 +(% style="color:#037691" %)**Battery:** 90 90 91 -Measure Volume: Base on the centra pin of the probe, a cylinder with 7cm diameter and 10cm height. 92 +* Li/SOCI2 un-chargeable battery 93 +* Capacity: 8500mAh 94 +* Self Discharge: <1% / Year @ 25°C 95 +* Max continuously current: 130mA 96 +* Max boost current: 2A, 1 second 92 92 93 - [[image:image-20220708101224-1.png]]98 +(% style="color:#037691" %)**Power Consumption** 94 94 100 +* STOP Mode: 10uA @ 3.3v 101 +* Max transmit power: 350mA@3.3v 95 95 96 96 97 97 == 1.4 Applications == 98 98 106 + 107 +* Smart Buildings & Home Automation 108 +* Logistics and Supply Chain Management 109 +* Smart Metering 99 99 * Smart Agriculture 111 +* Smart Cities 112 +* Smart Factory 100 100 101 101 (% class="wikigeneratedid" id="H200B1.5FirmwareChangelog" %) 102 102 103 103 117 + 104 104 == 1.5 Pin Definitions == 105 105 106 106 107 -[[image:16572 46476176-652.png]]121 +[[image:1657328609906-564.png]] 108 108 109 109 124 += 2. Use NDDS75 to communicate with IoT Server = 110 110 111 -= 2. Use NSE01 to communicate with IoT Server = 112 - 113 113 == 2.1 How it works == 114 114 115 115 116 116 ((( 117 -The NS E01is equipped with a NB-IoT module, the pre-loaded firmware in NSE01will 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 NSE01.130 +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. 118 118 ))) 119 119 120 120 121 121 ((( 122 -The diagram below shows the working flow in default firmware of NS E01:135 +The diagram below shows the working flow in default firmware of NDDS75: 123 123 ))) 124 124 125 -[[image:image-20220708101605-2.png]] 126 - 127 127 ((( 128 128 129 129 ))) 130 130 142 +[[image:1657328659945-416.png]] 131 131 144 +((( 145 + 146 +))) 132 132 133 -== 2.2 Configure the NS E01==148 +== 2.2 Configure the NDDS75 == 134 134 135 - 136 136 === 2.2.1 Test Requirement === 137 137 138 138 139 139 ((( 140 -To use NS E01in your city, make sure meet below requirements:154 +To use NDDS75 in your city, make sure meet below requirements: 141 141 ))) 142 142 143 143 * Your local operator has already distributed a NB-IoT Network there. 144 -* The local NB-IoT network used the band that NS E01supports.158 +* The local NB-IoT network used the band that NDDS75 supports. 145 145 * Your operator is able to distribute the data received in their NB-IoT network to your IoT server. 146 146 147 147 ((( 148 -Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8. The E01will 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 server162 +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. 149 149 ))) 150 150 151 151 152 -[[image:16572 49419225-449.png]]166 +[[image:1657328756309-230.png]] 153 153 154 154 155 - 156 156 === 2.2.2 Insert SIM card === 157 157 171 + 158 158 ((( 159 159 Insert the NB-IoT Card get from your provider. 160 160 ))) ... ... @@ -164,28 +164,30 @@ 164 164 ))) 165 165 166 166 167 -[[image:16572 49468462-536.png]]181 +[[image:1657328884227-504.png]] 168 168 169 169 184 +=== 2.2.3 Connect USB – TTL to NDDS75 to configure it === 170 170 171 -=== 2.2.3 Connect USB – TTL to NSE01 to configure it === 172 172 173 173 ((( 174 174 ((( 175 -User need to configure NS E01via serial port to set the (% style="color:blue" %)**Server Address** / **Uplink Topic** (%%)to define where and how-to uplink packets. NSE01support AT Commands, user can use a USB to TTL adapter to connect to NSE01and use AT Commands to configure it, as below.189 +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. 176 176 ))) 177 177 ))) 178 178 193 +[[image:image-20220709092052-2.png]] 179 179 180 -**Connection:** 181 181 182 - background-color:yellow" %)USB TTL GND <~-~-~-~-> GND196 +(% style="color:blue" %)**Connection:** 183 183 184 - (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~->UART_RXD198 + (% style="background-color:yellow" %)**USB TTL GND <~-~-~-~-> GND** 185 185 186 - (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD200 +**~ (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD(%%)** 187 187 202 +**~ (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD(%%)** 188 188 204 + 189 189 In the PC, use below serial tool settings: 190 190 191 191 * Baud: (% style="color:green" %)**9600** ... ... @@ -195,72 +195,87 @@ 195 195 * Flow Control: (% style="color:green" %)**None** 196 196 197 197 ((( 198 -Make sure the switch is in FLASH position, then power on device by connecting the jumper on NS E01. NSE01will output system info once power on as below, we can enter the (% style="color:green" %)**password: 12345678**(%%) to access AT Command input.214 +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. 199 199 ))) 200 200 201 -[[image: image-20220708110657-3.png]]217 +[[image:1657329814315-101.png]] 202 202 219 + 203 203 ((( 204 -(% style="color:red" %)Note: the valid AT Commands can be found at: (%%)[[http:~~/~~/www.dr agino.com/downloads/index.php?dir=NB-IoT/NSE01/>>url:http://www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN50/]]221 +(% style="color:red" %)**Note: the valid AT Commands can be found at: **(%%)**[[https:~~/~~/www.dropbox.com/sh/aaq2xcl0bzfu0yd/AAAEAHRa7Io_465ds4Y7-F3aa?dl=0>>https://www.dropbox.com/sh/aaq2xcl0bzfu0yd/AAAEAHRa7Io_465ds4Y7-F3aa?dl=0]]** 205 205 ))) 206 206 207 207 208 - 209 209 === 2.2.4 Use CoAP protocol to uplink data === 210 210 211 -(% 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/]] 212 212 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/]]** 213 213 230 + 231 +((( 214 214 **Use below commands:** 233 +))) 215 215 216 -* (% style="color:blue" %)**AT+PRO=1** (%%) ~/~/ Set to use CoAP protocol to uplink 217 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683 ** (%%)~/~/ to set CoAP server address and port 218 -* (% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path 235 +* ((( 236 +(% style="color:blue" %)**AT+PRO=1** (%%) ~/~/ Set to use CoAP protocol to uplink 237 +))) 238 +* ((( 239 +(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683 ** (%%)~/~/ to set CoAP server address and port 240 +))) 241 +* ((( 242 +(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/ Set COAP resource path 219 219 244 + 245 + 246 +))) 247 + 248 +((( 220 220 For parameter description, please refer to AT command set 221 221 222 -[[image:1657249793983-486.png]] 251 + 252 +))) 223 223 254 +[[image:1657330452568-615.png]] 224 224 225 -After configure the server address and (% style="color:green" %)**reset the device**(%%) (via AT+ATZ ), NSE01 will start to uplink sensor values to CoAP server. 226 226 227 -[[image:1657249831934-534.png]] 228 228 258 +((( 259 +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. 229 229 261 + 262 +))) 230 230 231 - === 2.2.5 Use UDP protocol to uplink data(Defaultprotocol) ===264 +[[image:1657330472797-498.png]] 232 232 233 -This feature is supported since firmware version v1.0.1 234 234 267 +=== 2.2.5 Use UDP protocol to uplink data(Default protocol) === 235 235 236 -* (% style="color:blue" %)**AT+PRO=2 ** (%%) ~/~/ Set to use UDP protocol to uplink 237 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601 ** (%%) ~/~/ to set UDP server address and port 238 -* (% style="color:blue" %)**AT+CFM=1 ** (%%) ~/~/If the server does not respond, this command is unnecessary 239 239 240 -[[image:1657249864775-321.png]] 270 +* (% style="color:blue" %)**AT+PRO=2 ** (%%) ~/~/ Set to use UDP protocol to uplink 271 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601 ** (%%) ~/~/ to set UDP server address and port 272 +* (% style="color:blue" %)**AT+CFM=1 ** (%%) ~/~/ If the server does not respond, this command is unnecessary 241 241 274 +[[image:1657330501006-241.png]] 242 242 243 -[[image:1657249930215-289.png]] 244 244 277 +[[image:1657330533775-472.png]] 245 245 246 246 247 247 === 2.2.6 Use MQTT protocol to uplink data === 248 248 249 -This feature is supported since firmware version v110 250 250 283 +* (% style="color:blue" %)**AT+PRO=3 ** (%%) ~/~/ Set to use MQTT protocol to uplink 284 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) ~/~/ Set MQTT server address and port 285 +* (% style="color:blue" %)**AT+CLIENT=CLIENT ** (%%)~/~/ Set up the CLIENT of MQTT 286 +* (% style="color:blue" %)**AT+UNAME=UNAME **(%%)~/~/ Set the username of MQTT 287 +* (% style="color:blue" %)**AT+PWD=PWD **(%%)~/~/ Set the password of MQTT 288 +* (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB **(%%)~/~/ Set the sending topic of MQTT 289 +* (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB **(%%) ~/~/ Set the subscription topic of MQTT 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=NSE01_PUB **(%%)~/~/Set the sending topic of MQTT 258 -* (% style="color:blue" %)**AT+SUBTOPIC=NSE01_SUB **(%%) ~/~/Set the subscription topic of MQTT 259 - 260 260 [[image:1657249978444-674.png]] 261 261 262 262 263 -[[image:16572 49990869-686.png]]294 +[[image:1657330723006-866.png]] 264 264 265 265 266 266 ((( ... ... @@ -268,78 +268,125 @@ 268 268 ))) 269 269 270 270 271 - 272 272 === 2.2.7 Use TCP protocol to uplink data === 273 273 274 -This feature is supported since firmware version v110 275 275 305 +* (% style="color:blue" %)**AT+PRO=4 ** (%%) ~/~/ Set to use TCP protocol to uplink 306 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600 **(%%) ~/~/ to set TCP server address and port 276 276 277 -* (% style="color:blue" %)**AT+PRO=4 ** (%%) ~/~/ Set to use TCP protocol to uplink 278 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600 **(%%) ~/~/ to set TCP server address and port 308 +[[image:image-20220709093918-1.png]] 279 279 280 -[[image:1657250217799-140.png]] 281 281 311 +[[image:image-20220709093918-2.png]] 282 282 283 -[[image:1657250255956-604.png]] 284 284 285 - 286 - 287 287 === 2.2.8 Change Update Interval === 288 288 316 + 289 289 User can use below command to change the (% style="color:green" %)**uplink interval**. 290 290 291 -* (% style="color:blue" %)**AT+TDC=600 ** (%%)~/~/ Set Update Interval to 600s 319 +* (% style="color:blue" %)**AT+TDC=600 ** (%%)~/~/ Set Update Interval to 600s 292 292 293 293 ((( 322 + 323 + 324 + 294 294 (% style="color:red" %)**NOTE:** 295 -))) 296 296 297 -((( 298 -(% style="color:red" %)1. By default, the device will send an uplink message every 1 hour. 327 +(% style="color:red" %)**1. By default, the device will send an uplink message every 1 hour.** 328 + 329 +(% style="color:red" %)**2. When the firmware version is v1.3.2 and later firmware:** 299 299 ))) 300 300 332 +(% 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).** 301 301 302 302 303 303 == 2.3 Uplink Payload == 304 304 305 - Inthismode,uplink payload includesin total18bytes337 +=== 2.3.1 Before Firmware v1.3.2 === 306 306 307 -(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:510px" %) 308 -|=(% style="width: 60px;" %)((( 339 + 340 +In this mode, uplink payload includes in total 14 bytes 341 + 342 +(% border="1" cellspacing="10" style="background-color:#f2f2f2; width:440px" %) 343 +|=(% style="width: 60px;background-color:#D9E2F3;color:#0070C0" %)((( 309 309 **Size(bytes)** 310 -)))|=(% style="width: 50px;" %)**6**|=(% style="width:25px;" %)2|=(% style="width:25px;" %)**2**|=(% style="width:70px;" %)**1**|=(% style="width:60px;" %)**2**|=(% style="width:80px;" %)**2**|=(% style="width:90px;" %)**2**|=(% style="width:50px;" %)**1**311 -|(% 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:10 8px" %)[[Soil Moisture>>||anchor="H2.4.5A0SoilMoisture"]]|(%style="width:133px"%)[[Soil Temperature>>||anchor="H2.4.6A0SoilTemperature"]]|(%style="width:159px" %)[[Soil Conductivity(EC)>>||anchor="H2.4.7A0SoilConductivity28EC29"]]|(% style="width:80px" %)[[Interrupt>>||anchor="H2.4.8A0DigitalInterrupt"]]345 +)))|=(% style="width: 60px;background-color:#D9E2F3;color:#0070C0" %)**6**|=(% style="width: 35px;background-color:#D9E2F3;color:#0070C0" %)2|=(% style="width: 35px;background-color:#D9E2F3;color:#0070C0" %)**2**|=(% style="width: 80px;background-color:#D9E2F3;color:#0070C0" %)**1**|=(% style="width: 100px;background-color:#D9E2F3;color:#0070C0" %)**2**|=(% style="width: 60px;background-color:#D9E2F3;color:#0070C0" %)**1** 346 +|(% 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"]] 312 312 313 313 ((( 314 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NS E01uplink data.349 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS75 uplink data. 315 315 ))) 316 316 317 317 318 -[[image: image-20220708111918-4.png]]353 +[[image:1657331036973-987.png]] 319 319 320 320 356 +The payload is **ASCII** string, representative same HEX: 357 + 358 +(% style="background-color:yellow" %)**0x 724031556159 0064 0c6c 19 0292 00 ** 359 + 360 +**where :** 361 + 362 +* (% style="color:#037691" %)**Device ID:**(%%) 0x724031556159 = 724031556159 363 + 364 +* (% style="color:#037691" %)**Version:**(%%) 0x0064=100=1.0.0 365 + 366 +* (% style="color:#037691" %)**BAT:** (%%) 0x0c6c = 3180 mV = 3.180V 367 + 368 +* (% style="color:#037691" %)**Signal:**(%%) 0x19 = 25 369 + 370 +* (% style="color:#037691" %)**Distance:** (%%)0x0292= 658 mm 371 + 372 +* (% style="color:#037691" %)**Interrupt:**(%%) 0x00 = 0 373 + 374 +=== 2.3.2 Since firmware v1.3.2 === 375 + 376 + 377 +In this mode, uplink payload includes 69 bytes in total by default. 378 + 379 +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. 380 + 381 +(% border="1" style="background-color:#f2f2f2; width:490px" %) 382 +|=(% style="width: 60px;background-color:#D9E2F3;color:#0070C0" %)**Size(bytes)**|(% style="width:40px;background-color:#D9E2F3;color:#0070C0" %)**8**|(% style="width:25px;background-color:#D9E2F3;color:#0070C0" %)**2**|(% style="width:25px;background-color:#D9E2F3;color:#0070C0" %)**2**|(% style="width:60px;background-color:#D9E2F3;color:#0070C0" %)**1**|(% style="width:25px;background-color:#D9E2F3;color:#0070C0" %)**1**|(% style="width:40px;background-color:#D9E2F3;color:#0070C0" %)**1**|(% style="width:40px;background-color:#D9E2F3;color:#0070C0" %)**2**|(% style="width:70px;background-color:#D9E2F3;color:#0070C0" %)**4**|(% style="width:40px;background-color:#D9E2F3;color:#0070C0" %)**2**|(% style="width:60px;background-color:#D9E2F3;color:#0070C0" %)**4** 383 +|=(% style="width: 95px;" %)**Value**|(% style="width:84px" %)Device ID|(% style="width:44px" %)Ver|(% style="width:48px" %)BAT|(% style="width:123px" %)Signal Strength|(% style="width:55px" %)MOD|(% style="width:80px" %)Interrupt|(% style="width:77px" %)Distance|(% style="width:94px" %)Timestamp|(% style="width:77px" %)Distance|(% style="width:116px" %)Timestamp....... 384 + 385 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS75 uplink data. 386 + 387 +[[image:image-20220908175246-1.png]] 388 + 389 + 321 321 The payload is ASCII string, representative same HEX: 322 322 323 -0x7240315561 5900640c7817075e0a8c02f900where:392 +**0x (% style="color:red" %)f867787050213317 (% style="color:blue" %)0084 (% style="color:green" %)0cf4 (% style="color:#00b0f0" %)1e (% style="color:#7030a0" %)01 (% style="color:#d60093" %)00(% style="color:#a14d07" %) 0039 (% style="color:#0020b0" %)6315537b (% style="color:#663300" %)00396319baf0 00396319ba3c 00396319b988 00396319b8d4 00396319b820 00396319b76c 00396319b6b8 00396319b604 (%%)** 324 324 325 -* Device ID: 0x 724031556159 = 724031556159 326 -* Version: 0x0064=100=1.0.0 394 +**where:** 327 327 328 -* BAT: 0x0c78 = 3192 mV = 3.192V 329 -* Singal: 0x17 = 23 330 -* Soil Moisture: 0x075e= 1886 = 18.86 % 331 -* Soil Temperature:0x0a8c =2700=27 °C 332 -* Soil Conductivity(EC) = 0x02f9 =761 uS /cm 333 -* Interrupt: 0x00 = 0 396 +* (% style="color:#037691" %)**Device ID:**(%%) f867787050213317 = f867787050213317 334 334 398 +* (% style="color:#037691" %)**Version:**(%%) 0x0084=132=1.3.2 335 335 400 +* (% style="color:#037691" %)**BAT:**(%%) 0x0cf4 = 3316 mV = 3.316V 336 336 402 +* (% style="color:#037691" %)**Singal:**(%%) 0x1e = 30 337 337 338 - ==2.4Payload ExplanationandSensorInterface==404 +* (% style="color:#037691" %)**Mod:**(%%)** **0x01 = 1 339 339 406 +* (% style="color:#037691" %)**Interrupt:**(%%) 0x00= 0 340 340 408 +* (% style="color:#037691" %)**Distance:**(%%) 0x0039= 57 = 57 409 + 410 +* (% style="color:#037691" %)**Time stamp:**(%%) 0x6315537b =1662342011 ([[Unix Epoch Time>>url:http://www.epochconverter.com/]]) 411 + 412 +* (% style="color:#037691" %)**Distance,Time stamp:**(%%) 00396319baf0 413 + 414 +* (% style="color:#037691" %)**8 sets of recorded data: Distance,Time stamp :**(%%) //**00396319ba3c**//,....... 415 + 416 +== 2.4 Payload Explanation and Sensor Interface == 417 + 341 341 === 2.4.1 Device ID === 342 342 420 + 343 343 ((( 344 344 By default, the Device ID equal to the last 6 bytes of IMEI. 345 345 ))) ... ... @@ -346,10 +346,12 @@ 346 346 347 347 ((( 348 348 User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID 427 + 428 + 349 349 ))) 350 350 351 351 ((( 352 -**Example:** 432 +(% style="color:blue" %)**Example :** 353 353 ))) 354 354 355 355 ((( ... ... @@ -357,28 +357,36 @@ 357 357 ))) 358 358 359 359 ((( 360 -The Device ID is stored in a none-erase area, Upgrade the firmware or run AT+FDR won't erase Device ID. 440 +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. 361 361 ))) 362 362 363 363 444 +(% style="color:red" %)**NOTE: When the firmware version is v1.3.2 and later firmware:** 364 364 446 +(% style="color:red" %)**By default, the Device ID equal to the last 15 bits of IMEI.** 447 + 448 +User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID 449 + 450 + 451 +(% style="color:blue" %)**Example :** 452 + 453 +AT+DEUI=868411056754138 454 + 455 + 365 365 === 2.4.2 Version Info === 366 366 458 + 367 367 ((( 368 368 Specify the software version: 0x64=100, means firmware version 1.00. 369 369 ))) 370 370 371 371 ((( 372 -For example: 0x00 64 : this device is NS E01with firmware version 1.0.0.464 +For example: 0x00 64 : this device is NDDS75 with firmware version 1.0.0. 373 373 ))) 374 374 375 375 376 - 377 377 === 2.4.3 Battery Info === 378 378 379 -((( 380 -Check the battery voltage for LSE01. 381 -))) 382 382 383 383 ((( 384 384 Ex1: 0x0B45 = 2885mV ... ... @@ -389,9 +389,9 @@ 389 389 ))) 390 390 391 391 392 - 393 393 === 2.4.4 Signal Strength === 394 394 482 + 395 395 ((( 396 396 NB-IoT Network signal Strength. 397 397 ))) ... ... @@ -421,77 +421,30 @@ 421 421 ))) 422 422 423 423 512 +=== 2.4.5 Distance === 424 424 425 -=== 2.4.5 Soil Moisture === 426 426 427 -((( 428 -((( 429 -Get the moisture content of the soil. The value range of the register is 0-10000(Decimal), divide this value by 100 to get the percentage of moisture in the soil. 430 -))) 431 -))) 515 +Get the distance. Flat object range 280mm - 7500mm. 432 432 433 433 ((( 434 -((( 435 -For example, if the data you get from the register is **__0x05 0xDC__**, the moisture content in the soil is 518 +For example, if the data you get from the register is **__0x0B 0x05__**, the distance between the sensor and the measured object is 436 436 ))) 437 -))) 438 438 439 439 ((( 440 - 441 -))) 442 - 443 443 ((( 444 -(% style="color: #4f81bd" %)**05DC(H) = 1500(D)/100= 15%.**523 +(% style="color:blue" %)** 0B05(H) = 2821(D) = 2821mm.** 445 445 ))) 446 - 447 - 448 - 449 -=== 2.4.6 Soil Temperature === 450 - 451 -((( 452 -Get the temperature in the soil. The value range of the register is -4000 - +800(Decimal), divide this value by 100 to get the temperature in the soil. For example, if the data you get from the register is __**0x09 0xEC**__, the temperature content in the soil is 453 453 ))) 454 454 455 455 ((( 456 -**Example**: 457 -))) 458 - 459 -((( 460 -If payload is 0105H: ((0x0105 & 0x8000)>>15 === 0),temp = 0105(H)/100 = 2.61 °C 461 -))) 462 - 463 -((( 464 -If payload is FF7EH: ((FF7E & 0x8000)>>15 ===1),temp = (FF7E(H)-FFFF(H))/100 = -1.29 °C 465 -))) 466 - 467 - 468 - 469 -=== 2.4.7 Soil Conductivity (EC) === 470 - 471 -((( 472 -Obtain (% style="color:#4f81bd" %)**__soluble salt concentration__**(%%) in soil or (% style="color:#4f81bd" %)**__soluble ion concentration in liquid fertilizer__**(%%) or (% style="color:#4f81bd" %)**__planting medium__**(%%). The value range of the register is 0 - 20000(Decimal)( Can be greater than 20000). 473 -))) 474 - 475 -((( 476 -For example, if the data you get from the register is __**0x00 0xC8**__, the soil conductivity is 00C8(H) = 200(D) = 200 uS/cm. 477 -))) 478 - 479 -((( 480 -Generally, the EC value of irrigation water is less than 800uS / cm. 481 -))) 482 - 483 -((( 484 484 485 485 ))) 486 486 487 -((( 488 - 489 -))) 531 +=== 2.4.6 Digital Interrupt === 490 490 491 -=== 2.4.8 Digital Interrupt === 492 492 493 493 ((( 494 -Digital Interrupt refers to pin (% style="color:blue" %)**GPIO_EXTI**(%%), and there are different trigger methods. When there is a trigger, the NS E01will send a packet to the server.535 +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. 495 495 ))) 496 496 497 497 ((( ... ... @@ -499,7 +499,7 @@ 499 499 ))) 500 500 501 501 ((( 502 -(% 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]])**.** 543 +(% 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]])**.** 503 503 ))) 504 504 505 505 ... ... @@ -521,20 +521,24 @@ 521 521 ))) 522 522 523 523 565 +=== 2.4.7 +5V Output === 524 524 525 -=== 2.4.9 +5V Output === 526 526 527 527 ((( 528 -NS E01will enable +5V output before all sampling and disable the +5v after all sampling.569 +NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling. 529 529 ))) 530 530 531 531 532 532 ((( 533 533 The 5V output time can be controlled by AT Command. 575 + 576 + 534 534 ))) 535 535 536 536 ((( 537 537 (% style="color:blue" %)**AT+5VT=1000** 581 + 582 + 538 538 ))) 539 539 540 540 ((( ... ... @@ -542,14 +542,14 @@ 542 542 ))) 543 543 544 544 545 - 546 546 == 2.5 Downlink Payload == 547 547 548 -By default, NSE01 prints the downlink payload to console port. 549 549 550 - [[image:image-20220708133731-5.png]]593 +By default, NDDS75 prints the downlink payload to console port. 551 551 595 +[[image:image-20220709100028-1.png]] 552 552 597 + 553 553 ((( 554 554 (% style="color:blue" %)**Examples:** 555 555 ))) ... ... @@ -583,7 +583,7 @@ 583 583 ))) 584 584 585 585 ((( 586 -If payload = 0x04FF, it will reset the NS E01631 +If payload = 0x04FF, it will reset the NDDS75 587 587 ))) 588 588 589 589 ... ... @@ -594,239 +594,195 @@ 594 594 ))) 595 595 596 596 642 +== 2.6 Distance alarm function(Since firmware v1.3.2) == 597 597 598 -== 2.6 LED Indicator == 599 599 600 -((( 601 -The NSE01 has an internal LED which is to show the status of different state. 645 +(% style="color:blue" %)** ➢ AT Command:** 602 602 647 +(% style="color:#037691" %)** AT+ LDDSALARM=min,max** 603 603 604 -* When power on, NSE01 will detect if sensor probe is connected, if probe detected, LED will blink four times. (no blinks in this step is no probe) 605 -* Then the LED will be on for 1 second means device is boot normally. 606 -* After NSE01 join NB-IoT network. The LED will be ON for 3 seconds. 607 -* For each uplink probe, LED will be on for 500ms. 608 -))) 649 +² When min=0, and max≠0, Alarm higher than max 609 609 651 +² When min≠0, and max=0, Alarm lower than min 610 610 653 +² When min≠0 and max≠0, Alarm higher than max or lower than min 611 611 612 612 613 - ==2.7 InstallationinSoil==656 +(% style="color:blue" %)** Example:** 614 614 615 - __**Measurementthesoilsurface**__658 +**AT+ LDDSALARM=260,2000** ~/~/ Alarm when distance lower than 260. 616 616 617 -((( 618 -Choose the proper measuring position. Avoid the probe to touch rocks or hard things. Split the surface soil according to the measured deep. Keep the measured as original density. Vertical insert the probe into the soil to be measured. Make sure not shake when inserting. [[https:~~/~~/img.alicdn.com/imgextra/i3/2005165265/O1CN010rj9Oh1olPsQxrdUK_!!2005165265.jpg>>url:https://img.alicdn.com/imgextra/i3/2005165265/O1CN010rj9Oh1olPsQxrdUK_!!2005165265.jpg]] 619 -))) 620 620 621 - [[image:1657259653666-883.png]]661 +== 2.7 Set the number of data to be uploaded and the recording time == 622 622 623 623 624 -((( 625 - 664 +(% style="color:blue" %)** ➢ AT Command:** 626 626 627 -((( 628 -Dig a hole with diameter > 20CM. 629 -))) 666 +* (% 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) 667 +* (% 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. 630 630 631 -((( 632 -Horizontal insert the probe to the soil and fill the hole for long term measurement. 633 -))) 634 -))) 669 + The diagram below explains the relationship between TR, NOUD, and TDC more clearly**:** 635 635 636 -[[image:1 654506665940-119.png]]671 +[[image:image-20221009001114-1.png||height="687" width="955"]] 637 637 638 -((( 639 - 640 -))) 641 641 674 +== 2.8 Read or Clear cached data == 642 642 643 -== 2.8 Firmware Change Log == 644 644 677 +(% style="color:blue" %)** ➢ AT Command:** 645 645 646 -Download URL & Firmware Change log 679 +* (% style="color:#037691" %)** AT+CDP ** (%%) ~/~/ Read cached data 680 +* (% style="color:#037691" %)** AT+CDP=0** (%%) ~/~/ Clear cached data 647 647 648 -[[ www.dragino.com/downloads/index.php?dir=NB-IoT/NSE01/Firmware/>>url:http://www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN50/Firmware/]]682 +[[image:image-20220908175333-2.png]] 649 649 650 650 651 - UpgradeInstruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]685 +== 2.9 LED Indicator == 652 652 653 653 688 +The NDDS75 has an internal LED which is to show the status of different state. 654 654 655 -== 2.9 Battery Analysis == 656 656 657 -=== 2.9.1 Battery Type === 691 +* 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) 692 +* Then the LED will be on for 1 second means device is boot normally. 693 +* After NDDS75 join NB-IoT network. The LED will be ON for 3 seconds. 694 +* For each uplink probe, LED will be on for 500ms. 658 658 659 - 660 660 ((( 661 - TheNSE01 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.697 + 662 662 ))) 663 663 664 664 665 -((( 666 -The battery is designed to last for several years depends on the actually use environment and update interval. 667 -))) 701 +== 2.10 Firmware Change Log == 668 668 669 669 670 670 ((( 671 - Thebatteryrelateddocumentsaselow:705 +Download URL & Firmware Change log: [[https:~~/~~/www.dropbox.com/sh/3hb94r49iszmstx/AADvSJcXxahEUfxqKWVnZx-La?dl=0>>https://www.dropbox.com/sh/3hb94r49iszmstx/AADvSJcXxahEUfxqKWVnZx-La?dl=0]] 672 672 ))) 673 673 674 -* [[Battery Dimension>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 675 -* [[Lithium-Thionyl Chloride Battery datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 676 -* [[Lithium-ion Battery-Capacitor datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 677 - 678 678 ((( 679 -[[ image:image-20220708140453-6.png]]709 +Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]] 680 680 ))) 681 681 682 682 713 +== 2.11 Battery & Power Consumption == 683 683 684 -=== 2.9.2 Power consumption Analyze === 685 685 686 -((( 687 -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. 688 -))) 716 +NDDS75 uses ER26500 + SPC1520 battery pack. See below link for detail information about the battery info and how to replace. 689 689 718 +[[**Battery Info & Power Consumption Analyze**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20calculate%20the%20battery%20life%20of%20Dragino%20sensors%3F/]] . 690 690 691 -((( 692 -Instruction to use as below: 693 -))) 694 694 695 -((( 696 -(% 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/]] 697 -))) 721 += 3. Access NB-IoT Module = 698 698 699 699 700 700 ((( 701 - (%style="color:blue"%)**Step2:**(%%) Openitandchoose725 +Users can directly access the AT command set of the NB-IoT module. 702 702 ))) 703 703 704 -* ((( 705 -Product Model 706 -))) 707 -* ((( 708 -Uplink Interval 709 -))) 710 -* ((( 711 -Working Mode 712 -))) 713 - 714 714 ((( 715 -And the Life expectation in difference case will be shown on the right. 716 -))) 729 +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/]] 717 717 718 -[[image:image-20220708141352-7.jpeg]] 719 - 720 - 721 - 722 -=== 2.9.3 Battery Note === 723 - 724 -((( 725 -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. 731 + 726 726 ))) 727 727 734 +[[image:1657333200519-600.png]] 728 728 729 729 730 -= ==2.9.4Replacethebattery===737 += 4. Using the AT Commands = 731 731 732 -((( 733 -The default battery pack of NSE01 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). 734 -))) 739 +== 4.1 Access AT Commands == 735 735 736 736 742 +See this link for detail: [[https:~~/~~/www.dropbox.com/sh/aaq2xcl0bzfu0yd/AAAEAHRa7Io_465ds4Y7-F3aa?dl=0>>https://www.dropbox.com/sh/aaq2xcl0bzfu0yd/AAAEAHRa7Io_465ds4Y7-F3aa?dl=0]] 737 737 738 -= 3. Access NB-IoT Module = 739 739 740 -((( 741 -Users can directly access the AT command set of the NB-IoT module. 742 -))) 745 +AT+<CMD>? : Help on <CMD> 743 743 744 -((( 745 -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/]] 746 -))) 747 +AT+<CMD> : Run <CMD> 747 747 748 - [[image:1657261278785-153.png]]749 +AT+<CMD>=<value> : Set the value 749 749 751 +AT+<CMD>=? : Get the value 750 750 751 751 752 - =4. UsingtheATCommands=754 +(% style="color:#037691" %)**General Commands**(%%) 753 753 754 - ==4.1AccessAT Commands==756 +AT : Attention 755 755 756 - Seethislinkfordetail:[[http:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/NSE01/>>url:http://www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN50/]]758 +AT? : Short Help 757 757 760 +ATZ : MCU Reset 758 758 759 -AT+ <CMD>?Helpon<CMD>762 +AT+TDC : Application Data Transmission Interval 760 760 761 -AT+ <CMD>Run<CMD>764 +AT+CFG : Print all configurations 762 762 763 -AT+ <CMD>=<value>: Setthevalue766 +AT+CFGMOD : Working mode selection 764 764 765 -AT+ <CMD>=?Get thevalue768 +AT+INTMOD : Set the trigger interrupt mode 766 766 770 +AT+5VT : Set extend the time of 5V power 767 767 768 - (%style="color:#037691"%)**GeneralCommands**(%%)772 +AT+PRO : Choose agreement 769 769 770 -AT : Attention774 +AT+WEIGRE : Get weight or set weight to 0 771 771 772 -AT ?: ShortHelp776 +AT+WEIGAP : Get or Set the GapValue of weight 773 773 774 -AT Z: MCU Reset778 +AT+RXDL : Extend the sending and receiving time 775 775 776 -AT+T DC: ApplicationData Transmission Interval780 +AT+CNTFAC : Get or set counting parameters 777 777 778 -AT+ CFGPrintall configurations782 +AT+SERVADDR : Server Address 779 779 780 -AT+ CFGMODWorkingmodeselection784 +AT+TR : Get or Set record time" 781 781 782 -AT+ INTMODSetthe triggerinterruptmode786 +AT+APN : Get or set the APN 783 783 784 -AT+ 5VT:Set extendthetimeof5V power788 +AT+FBAND : Get or Set whether to automatically modify the frequency band 785 785 786 -AT+ PRO: Chooseagreement790 +AT+DNSCFG : Get or Set DNS Server 787 787 788 -AT+ WEIGREGetweight or set weightto 0792 +AT+GETSENSORVALUE : Returns the current sensor measurement 789 789 790 -AT+ WEIGAP:Get or Set theGapValue ofweight794 +AT+NOUD : Get or Set the number of data to be uploaded 791 791 792 -AT+ RXDL: Extendthesendingandreceivingtime796 +AT+CDP : Read or Clear cached data 793 793 794 -AT+ CNTFACsetcounting parameters798 +AT+LDDSALARM : Get or Set alarm of distance 795 795 796 -AT+SERVADDR : Server Address 797 797 798 - 799 799 (% style="color:#037691" %)**COAP Management** 800 800 801 -AT+URI : Resource parameters 803 +AT+URI : Resource parameters 802 802 803 803 804 804 (% style="color:#037691" %)**UDP Management** 805 805 806 -AT+CFM : Upload confirmation mode (only valid for UDP) 808 +AT+CFM : Upload confirmation mode (only valid for UDP) 807 807 808 808 809 809 (% style="color:#037691" %)**MQTT Management** 810 810 811 -AT+CLIENT 813 +AT+CLIENT : Get or Set MQTT client 812 812 813 -AT+UNAME 815 +AT+UNAME : Get or Set MQTT Username 814 814 815 -AT+PWD 817 +AT+PWD : Get or Set MQTT password 816 816 817 -AT+PUBTOPIC 819 +AT+PUBTOPIC : Get or Set MQTT publish topic 818 818 819 -AT+SUBTOPIC 821 +AT+SUBTOPIC : Get or Set MQTT subscription topic 820 820 821 821 822 822 (% style="color:#037691" %)**Information** 823 823 824 -AT+FDR : Factory Data Reset 826 +AT+FDR : Factory Data Reset 825 825 826 -AT+PWORD : Serial Access Password 828 +AT+PWORD : Serial Access Password 827 827 828 828 829 - 830 830 = 5. FAQ = 831 831 832 832 == 5.1 How to Upgrade Firmware == ... ... @@ -841,11 +841,10 @@ 841 841 ))) 842 842 843 843 ((( 844 -(% style="color:red" %)Notice, NS E01and LSE01share the same mother board. They use the same connection and method to update.845 +(% style="color:red" %)**Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update.** 845 845 ))) 846 846 847 847 848 - 849 849 = 6. Trouble Shooting = 850 850 851 851 == 6.1 Connection problem when uploading firmware == ... ... @@ -860,26 +860,26 @@ 860 860 861 861 ))) 862 862 863 - 864 864 == 6.2 AT Command input doesn't work == 865 865 865 + 866 866 ((( 867 867 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. 868 868 ))) 869 869 870 870 871 +== 6.3 Not able to connect to NB-IoT network and keep showing "Signal Strength:99". == 871 871 872 -= 7. Order Info = 873 873 874 +This means sensor is trying to join the NB-IoT network but fail. Please see this link for **//[[trouble shooting for signal strenght:99>>doc:Main.CSQ\:99,99.WebHome]]//**. 874 874 875 -Part Number**:** (% style="color:#4f81bd" %)**NSE01** 876 876 877 += 7. Order Info = 877 877 878 -(% class="wikigeneratedid" %) 879 -((( 880 - 881 -))) 882 882 880 +Part Number**:** (% style="color:#4f81bd" %)**NSDDS75** 881 + 882 + 883 883 = 8. Packing Info = 884 884 885 885 ((( ... ... @@ -887,8 +887,7 @@ 887 887 888 888 (% style="color:#037691" %)**Package Includes**: 889 889 890 - 891 -* NSE01 NB-IoT Soil Moisture & EC Sensor x 1 890 +* NDDS75 NB-IoT Distance Detect Sensor Node x 1 892 892 * External antenna x 1 893 893 ))) 894 894 ... ... @@ -897,19 +897,21 @@ 897 897 898 898 (% style="color:#037691" %)**Dimension and weight**: 899 899 900 - 901 -* Size: 195 x 125 x 55 mm 902 -* Weight: 420g 899 +* Device Size: 13.0 x 5 x 4.5 cm 900 +* Device Weight: 150g 901 +* Package Size / pcs : 15 x 12x 5.5 cm 902 +* Weight / pcs : 220g 903 903 ))) 904 904 905 905 ((( 906 906 907 907 908 - 909 909 910 910 ))) 911 911 912 912 = 9. Support = 913 913 913 + 914 914 * 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. 915 + 915 915 * 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]]
- 1657271519014-786.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +71.5 KB - Content
- 1657327959271-447.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +78.3 KB - Content
- 1657328609906-564.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +492.6 KB - Content
- 1657328659945-416.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +78.8 KB - Content
- 1657328756309-230.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +78.5 KB - Content
- 1657328884227-504.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +483.6 KB - Content
- 1657329814315-101.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +85.3 KB - Content
- 1657330452568-615.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +71.3 KB - Content
- 1657330472797-498.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +68.9 KB - Content
- 1657330501006-241.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +119.2 KB - Content
- 1657330533775-472.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +74.9 KB - Content
- 1657330723006-866.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +74.1 KB - Content
- 1657331036973-987.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +83.8 KB - Content
- 1657332990863-496.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +138.2 KB - Content
- 1657333200519-600.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +126.1 KB - Content
- image-20220709084038-1.jpeg
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +72.0 KB - Content
- image-20220709084137-2.jpeg
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +72.0 KB - Content
- image-20220709084207-3.jpeg
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +72.0 KB - Content
- image-20220709084458-4.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +199.5 KB - Content
- image-20220709085040-1.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +200.4 KB - Content
- image-20220709092052-2.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +247.3 KB - Content
- image-20220709093918-1.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +42.2 KB - Content
- image-20220709093918-2.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +61.9 KB - Content
- image-20220709100028-1.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +8.8 KB - Content
- image-20220709101450-2.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +138.5 KB - Content
- image-20220709110451-3.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +611.5 KB - Content
- image-20220908175246-1.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.David - Size
-
... ... @@ -1,0 +1,1 @@ 1 +55.7 KB - Content
- image-20220908175333-2.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.David - Size
-
... ... @@ -1,0 +1,1 @@ 1 +31.1 KB - Content
- image-20221009001114-1.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Edwin - Size
-
... ... @@ -1,0 +1,1 @@ 1 +282.9 KB - Content