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 (1 modified, 0 added, 0 removed)
-
Attachments (0 modified, 24 added, 0 removed)
- 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-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
-
- Content
-
... ... @@ -1,13 +1,13 @@ 1 -[[image:image-20220709084207-3.jpeg||height="548" width="548"]] 1 +(% style="text-align:center" %) 2 +[[image:image-20220709085040-1.png||height="542" width="524"]] 2 2 3 3 4 4 5 5 6 6 7 - 8 - 9 9 **Table of Contents:** 10 10 10 +{{toc/}} 11 11 12 12 13 13 ... ... @@ -22,39 +22,55 @@ 22 22 23 23 24 24 ((( 25 +((( 25 25 The Dragino NDDS75 is a (% style="color:blue" %)**NB-IoT Distance Detection Sensor**(%%) for Internet of Things solution. It is designed to measure the distance between the sensor and a flat object. The distance detection sensor is a module that uses ultrasonic sensing technology for distance measurement, and temperature compensation is performed internally to improve the reliability of data. 26 -\\The NDDS75 can be applied to scenarios such as horizontal distance measurement, liquid level measurement, parking management system, object proximity and presence detection, intelligent trash can management system, robot obstacle avoidance, automatic control, sewer, bottom water level monitoring, etc. It detects the distance between the measured object and the sensor, and uploads the value via wireless to IoT Server via NB-IoT Network. 27 -\\NarrowBand-Internet of Things (NB-IoT) is a standards-based low power wide area (LPWA) technology developed to enable a wide range of new IoT devices and services. NB-IoT significantly improves the power consumption of user devices, system capacity and spectrum efficiency, especially in deep coverage. 28 -\\NDDS75 supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP and CoAP** (%%)for different application requirement. 29 -\\NDDS75 is powered by (% style="color:blue" %)**8500mAh Li-SOCI2 battery**(%%), It is designed for long term use up to 5 years. (Actually Battery life depends on the use environment, update period & uplink method) 30 -\\To use NDDS75, user needs to check if there is NB-IoT coverage in local area and with the bands NDDS75 supports. If the local operate support it, user needs to get a NB-IoT SIM card from local operator and install NDDS75 to get NB-IoT network connection. 31 31 ))) 32 32 33 - 29 +((( 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. 34 34 ))) 35 35 36 -[[image:1654503236291-817.png]] 33 +((( 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. 35 +))) 37 37 37 +((( 38 +NDDS75 supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP and CoAP** (%%)for different application requirement. 39 +))) 38 38 39 -[[image:1657245163077-232.png]] 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) 43 +))) 40 40 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 +))) 41 41 50 + 51 +))) 42 42 53 +[[image:1657327959271-447.png]] 54 + 55 + 43 43 == 1.2 Features == 44 44 58 + 45 45 * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD 46 -* Monitor Soil Moisture 47 -* Monitor Soil Temperature 48 -* 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 49 49 * AT Commands to change parameters 50 50 * Uplink on periodically 51 51 * Downlink to change configure 52 52 * IP66 Waterproof Enclosure 53 -* Ultra-Low Power consumption 54 -* AT Commands to change parameters 55 55 * Micro SIM card slot for NB-IoT SIM 56 56 * 8500mAh Battery for long term use 57 57 72 + 73 + 58 58 == 1.3 Specification == 59 59 60 60 ... ... @@ -65,82 +65,96 @@ 65 65 66 66 (% style="color:#037691" %)**NB-IoT Spec:** 67 67 68 -* -B1 @H-FDD: 2100MHz69 -* -B3 @H-FDD: 1800MHz70 -* -B8 @H-FDD: 900MHz71 -* -B5 @H-FDD: 850MHz72 -* -B20 @H-FDD: 800MHz73 -* -B28 @H-FDD: 700MHz84 +* B1 @H-FDD: 2100MHz 85 +* B3 @H-FDD: 1800MHz 86 +* B8 @H-FDD: 900MHz 87 +* B5 @H-FDD: 850MHz 88 +* B20 @H-FDD: 800MHz 89 +* B28 @H-FDD: 700MHz 74 74 75 - Probe(% style="color:#037691" %)**Specification:**91 +(% style="color:#037691" %)**Battery:** 76 76 77 -Measure Volume: Base on the centra pin of the probe, a cylinder with 7cm diameter and 10cm height. 93 +* Li/SOCI2 un-chargeable battery 94 +* Capacity: 8500mAh 95 +* Self Discharge: <1% / Year @ 25°C 96 +* Max continuously current: 130mA 97 +* Max boost current: 2A, 1 second 78 78 79 - [[image:image-20220708101224-1.png]]99 +(% style="color:#037691" %)**Power Consumption** 80 80 101 +* STOP Mode: 10uA @ 3.3v 102 +* Max transmit power: [[350mA@3.3v>>mailto:350mA@3.3v]] 81 81 82 82 105 + 83 83 == 1.4 Applications == 84 84 108 + 109 +* Smart Buildings & Home Automation 110 +* Logistics and Supply Chain Management 111 +* Smart Metering 85 85 * Smart Agriculture 113 +* Smart Cities 114 +* Smart Factory 86 86 87 87 (% class="wikigeneratedid" id="H200B1.5FirmwareChangelog" %) 88 88 89 89 119 + 90 90 == 1.5 Pin Definitions == 91 91 92 92 93 -[[image:16572 46476176-652.png]]123 +[[image:1657328609906-564.png]] 94 94 95 95 126 += 2. Use NDDS75 to communicate with IoT Server = 96 96 97 -= 2. Use NSE01 to communicate with IoT Server = 98 - 99 99 == 2.1 How it works == 100 100 101 101 102 102 ((( 103 -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.132 +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. 104 104 ))) 105 105 106 106 107 107 ((( 108 -The diagram below shows the working flow in default firmware of NS E01:137 +The diagram below shows the working flow in default firmware of NDDS75: 109 109 ))) 110 110 111 -[[image:image-20220708101605-2.png]] 112 - 113 113 ((( 114 114 115 115 ))) 116 116 144 +[[image:1657328659945-416.png]] 117 117 146 +((( 147 + 148 +))) 118 118 119 -== 2.2 Configure the NS E01==150 +== 2.2 Configure the NDDS75 == 120 120 121 - 122 122 === 2.2.1 Test Requirement === 123 123 124 124 125 125 ((( 126 -To use NS E01in your city, make sure meet below requirements:156 +To use NDDS75 in your city, make sure meet below requirements: 127 127 ))) 128 128 129 129 * Your local operator has already distributed a NB-IoT Network there. 130 -* The local NB-IoT network used the band that NS E01supports.160 +* The local NB-IoT network used the band that NDDS75 supports. 131 131 * Your operator is able to distribute the data received in their NB-IoT network to your IoT server. 132 132 133 133 ((( 134 -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 server164 +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. 135 135 ))) 136 136 137 137 138 -[[image:16572 49419225-449.png]]168 +[[image:1657328756309-230.png]] 139 139 140 140 141 - 142 142 === 2.2.2 Insert SIM card === 143 143 173 + 144 144 ((( 145 145 Insert the NB-IoT Card get from your provider. 146 146 ))) ... ... @@ -150,28 +150,30 @@ 150 150 ))) 151 151 152 152 153 -[[image:16572 49468462-536.png]]183 +[[image:1657328884227-504.png]] 154 154 155 155 186 +=== 2.2.3 Connect USB – TTL to NDDS75 to configure it === 156 156 157 -=== 2.2.3 Connect USB – TTL to NSE01 to configure it === 158 158 159 159 ((( 160 160 ((( 161 -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.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. 162 162 ))) 163 163 ))) 164 164 195 +[[image:image-20220709092052-2.png]] 165 165 166 -**Connection:** 167 167 168 - background-color:yellow" %)USB TTL GND <~-~-~-~-> GND198 +(% style="color:blue" %)**Connection:** 169 169 170 - (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~->UART_RXD200 + (% style="background-color:yellow" %)**USB TTL GND <~-~-~-~-> GND** 171 171 172 - (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD202 +**~ (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD(%%)** 173 173 204 +**~ (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD(%%)** 174 174 206 + 175 175 In the PC, use below serial tool settings: 176 176 177 177 * Baud: (% style="color:green" %)**9600** ... ... @@ -181,72 +181,87 @@ 181 181 * Flow Control: (% style="color:green" %)**None** 182 182 183 183 ((( 184 -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.216 +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. 185 185 ))) 186 186 187 -[[image: image-20220708110657-3.png]]219 +[[image:1657329814315-101.png]] 188 188 221 + 189 189 ((( 190 -(% 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/]]223 +(% 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]]** 191 191 ))) 192 192 193 193 194 - 195 195 === 2.2.4 Use CoAP protocol to uplink data === 196 196 197 -(% 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/]] 198 198 230 +(% 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/]]** 199 199 232 + 233 +((( 200 200 **Use below commands:** 235 +))) 201 201 202 -* (% style="color:blue" %)**AT+PRO=1** (%%) ~/~/ Set to use CoAP protocol to uplink 203 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683 ** (%%)~/~/ to set CoAP server address and port 204 -* (% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path 237 +* ((( 238 +(% style="color:blue" %)**AT+PRO=1** (%%) ~/~/ Set to use CoAP protocol to uplink 239 +))) 240 +* ((( 241 +(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683 ** (%%)~/~/ to set CoAP server address and port 242 +))) 243 +* ((( 244 +(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/ Set COAP resource path 205 205 246 + 247 + 248 +))) 249 + 250 +((( 206 206 For parameter description, please refer to AT command set 207 207 208 -[[image:1657249793983-486.png]] 253 + 254 +))) 209 209 256 +[[image:1657330452568-615.png]] 210 210 211 -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. 212 212 213 -[[image:1657249831934-534.png]] 214 214 260 +((( 261 +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. 215 215 263 + 264 +))) 216 216 217 - === 2.2.5 Use UDP protocol to uplink data(Defaultprotocol) ===266 +[[image:1657330472797-498.png]] 218 218 219 -This feature is supported since firmware version v1.0.1 220 220 269 +=== 2.2.5 Use UDP protocol to uplink data(Default protocol) === 221 221 222 -* (% style="color:blue" %)**AT+PRO=2 ** (%%) ~/~/ Set to use UDP protocol to uplink 223 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601 ** (%%) ~/~/ to set UDP server address and port 224 -* (% style="color:blue" %)**AT+CFM=1 ** (%%) ~/~/If the server does not respond, this command is unnecessary 225 225 226 -[[image:1657249864775-321.png]] 272 +* (% style="color:blue" %)**AT+PRO=2 ** (%%) ~/~/ Set to use UDP protocol to uplink 273 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601 ** (%%) ~/~/ to set UDP server address and port 274 +* (% style="color:blue" %)**AT+CFM=1 ** (%%) ~/~/ If the server does not respond, this command is unnecessary 227 227 276 +[[image:1657330501006-241.png]] 228 228 229 -[[image:1657249930215-289.png]] 230 230 279 +[[image:1657330533775-472.png]] 231 231 232 232 233 233 === 2.2.6 Use MQTT protocol to uplink data === 234 234 235 -This feature is supported since firmware version v110 236 236 285 +* (% style="color:blue" %)**AT+PRO=3 ** (%%) ~/~/ Set to use MQTT protocol to uplink 286 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) ~/~/ Set MQTT server address and port 287 +* (% style="color:blue" %)**AT+CLIENT=CLIENT ** (%%)~/~/ Set up the CLIENT of MQTT 288 +* (% style="color:blue" %)**AT+UNAME=UNAME **(%%)~/~/ Set the username of MQTT 289 +* (% style="color:blue" %)**AT+PWD=PWD **(%%)~/~/ Set the password of MQTT 290 +* (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB **(%%)~/~/ Set the sending topic of MQTT 291 +* (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB **(%%) ~/~/ Set the subscription topic of MQTT 237 237 238 -* (% style="color:blue" %)**AT+PRO=3 ** (%%) ~/~/Set to use MQTT protocol to uplink 239 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) ~/~/Set MQTT server address and port 240 -* (% style="color:blue" %)**AT+CLIENT=CLIENT ** (%%)~/~/Set up the CLIENT of MQTT 241 -* (% style="color:blue" %)**AT+UNAME=UNAME **(%%)~/~/Set the username of MQTT 242 -* (% style="color:blue" %)**AT+PWD=PWD **(%%)~/~/Set the password of MQTT 243 -* (% style="color:blue" %)**AT+PUBTOPIC=NSE01_PUB **(%%)~/~/Set the sending topic of MQTT 244 -* (% style="color:blue" %)**AT+SUBTOPIC=NSE01_SUB **(%%) ~/~/Set the subscription topic of MQTT 245 - 246 246 [[image:1657249978444-674.png]] 247 247 248 248 249 -[[image:16572 49990869-686.png]]296 +[[image:1657330723006-866.png]] 250 250 251 251 252 252 ((( ... ... @@ -254,75 +254,129 @@ 254 254 ))) 255 255 256 256 257 - 258 258 === 2.2.7 Use TCP protocol to uplink data === 259 259 260 -This feature is supported since firmware version v110 261 261 307 +* (% style="color:blue" %)**AT+PRO=4 ** (%%) ~/~/ Set to use TCP protocol to uplink 308 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600 **(%%) ~/~/ to set TCP server address and port 262 262 263 -* (% style="color:blue" %)**AT+PRO=4 ** (%%) ~/~/ Set to use TCP protocol to uplink 264 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600 **(%%) ~/~/ to set TCP server address and port 310 +[[image:image-20220709093918-1.png]] 265 265 266 -[[image:1657250217799-140.png]] 267 267 313 +[[image:image-20220709093918-2.png]] 268 268 269 -[[image:1657250255956-604.png]] 270 270 271 - 272 - 273 273 === 2.2.8 Change Update Interval === 274 274 318 + 275 275 User can use below command to change the (% style="color:green" %)**uplink interval**. 276 276 277 -* (% style="color:blue" %)**AT+TDC=600 ** (%%)~/~/ Set Update Interval to 600s 321 +* (% style="color:blue" %)**AT+TDC=600 ** (%%)~/~/ Set Update Interval to 600s 278 278 279 279 ((( 324 + 325 + 326 + 280 280 (% style="color:red" %)**NOTE:** 281 -))) 282 282 283 -((( 284 -(% style="color:red" %)1. By default, the device will send an uplink message every 1 hour. 329 +(% style="color:red" %)**1. By default, the device will send an uplink message every 1 hour.** 330 + 331 +(% style="color:red" %)**2. When the firmware version is v1.3.2 and later firmware:** 285 285 ))) 286 286 334 +(% 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).** 287 287 288 288 289 289 == 2.3 Uplink Payload == 290 290 291 - Inthismode,uplink payload includesin total18bytes339 +=== 2.3.1 Before Firmware v1.3.2 === 292 292 293 -(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:510px" %) 341 + 342 +In this mode, uplink payload includes in total 14 bytes 343 + 344 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %) 294 294 |=(% style="width: 60px;" %)((( 295 295 **Size(bytes)** 296 -)))|=(% 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**297 -|(% 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"]]347 +)))|=(% style="width: 60px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 80px;" %)**1**|=(% style="width: 100px;" %)**2**|=(% style="width: 60px;" %)**1** 348 +|(% 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"]] 298 298 299 299 ((( 300 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NS E01uplink data.351 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS75 uplink data. 301 301 ))) 302 302 303 303 304 -[[image: image-20220708111918-4.png]]355 +[[image:1657331036973-987.png]] 305 305 306 306 358 +The payload is **ASCII** string, representative same HEX: 359 + 360 +(% style="background-color:yellow" %)**0x 724031556159 0064 0c6c 19 0292 00 ** 361 + 362 +**where :** 363 + 364 +* (% style="color:#037691" %)**Device ID:**(%%) 0x724031556159 = 724031556159 365 + 366 +* (% style="color:#037691" %)**Version:**(%%) 0x0064=100=1.0.0 367 + 368 +* (% style="color:#037691" %)**BAT:** (%%) 0x0c6c = 3180 mV = 3.180V 369 + 370 +* (% style="color:#037691" %)**Signal:**(%%) 0x19 = 25 371 + 372 +* (% style="color:#037691" %)**Distance:** (%%)0x0292= 658 mm 373 + 374 +* (% style="color:#037691" %)**Interrupt:**(%%) 0x00 = 0 375 + 376 + 377 + 378 +=== 2.3.2 Since firmware v1.3.2 === 379 + 380 + 381 +In this mode, uplink payload includes 69 bytes in total by default. 382 + 383 +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. 384 + 385 +(% border="1" style="background-color:#ffffcc; color:green; width:490px" %) 386 +|=(% scope="row" style="width: 60px;" %)**Size(bytes)**|(% style="width:40px" %)**8**|(% style="width:25px" %)**2**|(% style="width:25px" %)**2**|(% style="width:60px" %)**1**|(% style="width:25px" %)**1**|(% style="width:40px" %)**1**|(% style="width:40px" %)**2**|(% style="width:70px" %)**4**|(% style="width:40px" %)**2**|(% style="width:60px" %)**4** 387 +|=(% 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....... 388 + 389 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS75 uplink data. 390 + 391 +[[image:image-20220908175246-1.png]] 392 + 393 + 307 307 The payload is ASCII string, representative same HEX: 308 308 309 -0x7240315561 5900640c7817075e0a8c02f900where:396 +**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 (%%)** 310 310 311 -* Device ID: 0x 724031556159 = 724031556159 312 -* Version: 0x0064=100=1.0.0 398 +**where:** 313 313 314 -* BAT: 0x0c78 = 3192 mV = 3.192V 315 -* Singal: 0x17 = 23 316 -* Soil Moisture: 0x075e= 1886 = 18.86 % 317 -* Soil Temperature:0x0a8c =2700=27 °C 318 -* Soil Conductivity(EC) = 0x02f9 =761 uS /cm 319 -* Interrupt: 0x00 = 0 400 +* (% style="color:#037691" %)**Device ID:**(%%) f867787050213317 = f867787050213317 320 320 321 - ==2.4Payload Explanationand Sensor Interface==402 +* (% style="color:#037691" %)**Version:**(%%) 0x0084=132=1.3.2 322 322 404 +* (% style="color:#037691" %)**BAT:**(%%) 0x0cf4 = 3316 mV = 3.316V 323 323 406 +* (% style="color:#037691" %)**Singal:**(%%) 0x1e = 30 407 + 408 +* (% style="color:#037691" %)**Mod:**(%%)** **0x01 = 1 409 + 410 +* (% style="color:#037691" %)**Interrupt:**(%%) 0x00= 0 411 + 412 +* (% style="color:#037691" %)**Distance:**(%%) 0x0039= 57 = 57 413 + 414 +* (% style="color:#037691" %)**Time stamp:**(%%) 0x6315537b =1662342011 ([[Unix Epoch Time>>url:http://www.epochconverter.com/]]) 415 + 416 +* (% style="color:#037691" %)**Distance,Time stamp:**(%%) 00396319baf0 417 + 418 +* (% style="color:#037691" %)**8 sets of recorded data: Distance,Time stamp :**(%%) //**00396319ba3c**//,....... 419 + 420 + 421 + 422 +== 2.4 Payload Explanation and Sensor Interface == 423 + 324 324 === 2.4.1 Device ID === 325 325 426 + 326 326 ((( 327 327 By default, the Device ID equal to the last 6 bytes of IMEI. 328 328 ))) ... ... @@ -329,10 +329,12 @@ 329 329 330 330 ((( 331 331 User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID 433 + 434 + 332 332 ))) 333 333 334 334 ((( 335 -**Example:** 438 +(% style="color:blue" %)**Example :** 336 336 ))) 337 337 338 338 ((( ... ... @@ -340,28 +340,36 @@ 340 340 ))) 341 341 342 342 ((( 343 -The Device ID is stored in a none-erase area, Upgrade the firmware or run AT+FDR won't erase Device ID. 446 +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. 344 344 ))) 345 345 346 346 450 +(% style="color:red" %)**NOTE: When the firmware version is v1.3.2 and later firmware:** 347 347 452 +(% style="color:red" %)**By default, the Device ID equal to the last 15 bits of IMEI.** 453 + 454 +User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID 455 + 456 + 457 +(% style="color:blue" %)**Example :** 458 + 459 +AT+DEUI=868411056754138 460 + 461 + 348 348 === 2.4.2 Version Info === 349 349 464 + 350 350 ((( 351 351 Specify the software version: 0x64=100, means firmware version 1.00. 352 352 ))) 353 353 354 354 ((( 355 -For example: 0x00 64 : this device is NS E01with firmware version 1.0.0.470 +For example: 0x00 64 : this device is NDDS75 with firmware version 1.0.0. 356 356 ))) 357 357 358 358 359 - 360 360 === 2.4.3 Battery Info === 361 361 362 -((( 363 -Check the battery voltage for LSE01. 364 -))) 365 365 366 366 ((( 367 367 Ex1: 0x0B45 = 2885mV ... ... @@ -372,9 +372,9 @@ 372 372 ))) 373 373 374 374 375 - 376 376 === 2.4.4 Signal Strength === 377 377 488 + 378 378 ((( 379 379 NB-IoT Network signal Strength. 380 380 ))) ... ... @@ -404,77 +404,30 @@ 404 404 ))) 405 405 406 406 518 +=== 2.4.5 Distance === 407 407 408 -=== 2.4.5 Soil Moisture === 409 409 410 -((( 411 -((( 412 -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. 413 -))) 414 -))) 521 +Get the distance. Flat object range 280mm - 7500mm. 415 415 416 416 ((( 417 -((( 418 -For example, if the data you get from the register is **__0x05 0xDC__**, the moisture content in the soil is 524 +For example, if the data you get from the register is **__0x0B 0x05__**, the distance between the sensor and the measured object is 419 419 ))) 420 -))) 421 421 422 422 ((( 423 - 424 -))) 425 - 426 426 ((( 427 -(% style="color: #4f81bd" %)**05DC(H) = 1500(D)/100= 15%.**529 +(% style="color:blue" %)** 0B05(H) = 2821(D) = 2821mm.** 428 428 ))) 429 - 430 - 431 - 432 -=== 2.4.6 Soil Temperature === 433 - 434 -((( 435 -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 436 436 ))) 437 437 438 438 ((( 439 -**Example**: 440 -))) 441 - 442 -((( 443 -If payload is 0105H: ((0x0105 & 0x8000)>>15 === 0),temp = 0105(H)/100 = 2.61 °C 444 -))) 445 - 446 -((( 447 -If payload is FF7EH: ((FF7E & 0x8000)>>15 ===1),temp = (FF7E(H)-FFFF(H))/100 = -1.29 °C 448 -))) 449 - 450 - 451 - 452 -=== 2.4.7 Soil Conductivity (EC) === 453 - 454 -((( 455 -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). 456 -))) 457 - 458 -((( 459 -For example, if the data you get from the register is __**0x00 0xC8**__, the soil conductivity is 00C8(H) = 200(D) = 200 uS/cm. 460 -))) 461 - 462 -((( 463 -Generally, the EC value of irrigation water is less than 800uS / cm. 464 -))) 465 - 466 -((( 467 467 468 468 ))) 469 469 470 -((( 471 - 472 -))) 537 +=== 2.4.6 Digital Interrupt === 473 473 474 -=== 2.4.8 Digital Interrupt === 475 475 476 476 ((( 477 -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.541 +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. 478 478 ))) 479 479 480 480 ((( ... ... @@ -482,7 +482,7 @@ 482 482 ))) 483 483 484 484 ((( 485 -(% 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]])**.** 549 +(% 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]])**.** 486 486 ))) 487 487 488 488 ... ... @@ -504,20 +504,24 @@ 504 504 ))) 505 505 506 506 571 +=== 2.4.7 +5V Output === 507 507 508 -=== 2.4.9 +5V Output === 509 509 510 510 ((( 511 -NS E01will enable +5V output before all sampling and disable the +5v after all sampling.575 +NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling. 512 512 ))) 513 513 514 514 515 515 ((( 516 516 The 5V output time can be controlled by AT Command. 581 + 582 + 517 517 ))) 518 518 519 519 ((( 520 520 (% style="color:blue" %)**AT+5VT=1000** 587 + 588 + 521 521 ))) 522 522 523 523 ((( ... ... @@ -525,14 +525,14 @@ 525 525 ))) 526 526 527 527 528 - 529 529 == 2.5 Downlink Payload == 530 530 531 -By default, NSE01 prints the downlink payload to console port. 532 532 533 - [[image:image-20220708133731-5.png]]599 +By default, NDDS75 prints the downlink payload to console port. 534 534 601 +[[image:image-20220709100028-1.png]] 535 535 603 + 536 536 ((( 537 537 (% style="color:blue" %)**Examples:** 538 538 ))) ... ... @@ -566,7 +566,7 @@ 566 566 ))) 567 567 568 568 ((( 569 -If payload = 0x04FF, it will reset the NS E01637 +If payload = 0x04FF, it will reset the NDDS75 570 570 ))) 571 571 572 572 ... ... @@ -577,239 +577,195 @@ 577 577 ))) 578 578 579 579 648 +== 2.6 Distance alarm function(Since firmware v1.3.2) == 580 580 581 -== 2.6 LED Indicator == 582 582 583 -((( 584 -The NSE01 has an internal LED which is to show the status of different state. 651 +(% style="color:blue" %)** ➢ AT Command:** 585 585 653 +(% style="color:#037691" %)** AT+ LDDSALARM=min,max** 586 586 587 -* 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) 588 -* Then the LED will be on for 1 second means device is boot normally. 589 -* After NSE01 join NB-IoT network. The LED will be ON for 3 seconds. 590 -* For each uplink probe, LED will be on for 500ms. 591 -))) 655 +² When min=0, and max≠0, Alarm higher than max 592 592 657 +² When min≠0, and max=0, Alarm lower than min 593 593 659 +² When min≠0 and max≠0, Alarm higher than max or lower than min 594 594 595 595 596 - ==2.7 InstallationinSoil==662 +(% style="color:blue" %)** Example:** 597 597 598 - __**Measurementthesoilsurface**__664 +**AT+ LDDSALARM=260,2000** ~/~/ Alarm when distance lower than 260. 599 599 600 -((( 601 -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]] 602 -))) 603 603 604 - [[image:1657259653666-883.png]]667 +== 2.7 Set the number of data to be uploaded and the recording time == 605 605 606 606 607 -((( 608 - 670 +(% style="color:blue" %)** ➢ AT Command:** 609 609 610 -((( 611 -Dig a hole with diameter > 20CM. 612 -))) 672 +* (% 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) 673 +* (% 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. 613 613 614 -((( 615 -Horizontal insert the probe to the soil and fill the hole for long term measurement. 616 -))) 617 -))) 675 + The diagram below explains the relationship between TR, NOUD, and TDC more clearly**:** 618 618 619 -[[image:1 654506665940-119.png]]677 +[[image:image-20221009001114-1.png||height="687" width="955"]] 620 620 621 -((( 622 - 623 -))) 624 624 680 +== 2.8 Read or Clear cached data == 625 625 626 -== 2.8 Firmware Change Log == 627 627 683 +(% style="color:blue" %)** ➢ AT Command:** 628 628 629 -Download URL & Firmware Change log 685 +* (% style="color:#037691" %)** AT+CDP ** (%%) ~/~/ Read cached data 686 +* (% style="color:#037691" %)** AT+CDP=0** (%%) ~/~/ Clear cached data 630 630 631 -[[ www.dragino.com/downloads/index.php?dir=NB-IoT/NSE01/Firmware/>>url:http://www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN50/Firmware/]]688 +[[image:image-20220908175333-2.png]] 632 632 633 633 634 - UpgradeInstruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]691 +== 2.9 LED Indicator == 635 635 636 636 694 +The NDDS75 has an internal LED which is to show the status of different state. 637 637 638 -== 2.9 Battery Analysis == 639 639 640 -=== 2.9.1 Battery Type === 697 +* 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) 698 +* Then the LED will be on for 1 second means device is boot normally. 699 +* After NDDS75 join NB-IoT network. The LED will be ON for 3 seconds. 700 +* For each uplink probe, LED will be on for 500ms. 641 641 642 - 643 643 ((( 644 - 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.703 + 645 645 ))) 646 646 647 647 648 -((( 649 -The battery is designed to last for several years depends on the actually use environment and update interval. 650 -))) 707 +== 2.10 Firmware Change Log == 651 651 652 652 653 653 ((( 654 - Thebatteryrelateddocumentsaselow:711 +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]] 655 655 ))) 656 656 657 -* [[Battery Dimension>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 658 -* [[Lithium-Thionyl Chloride Battery datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 659 -* [[Lithium-ion Battery-Capacitor datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 660 - 661 661 ((( 662 -[[ image:image-20220708140453-6.png]]715 +Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]] 663 663 ))) 664 664 665 665 719 +== 2.11 Battery & Power Consumption == 666 666 667 -=== 2.9.2 Power consumption Analyze === 668 668 669 -((( 670 -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. 671 -))) 722 +NDDS75 uses ER26500 + SPC1520 battery pack. See below link for detail information about the battery info and how to replace. 672 672 724 +[[**Battery Info & Power Consumption Analyze**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20calculate%20the%20battery%20life%20of%20Dragino%20sensors%3F/]] . 673 673 674 -((( 675 -Instruction to use as below: 676 -))) 677 677 678 -((( 679 -(% 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/]] 680 -))) 727 += 3. Access NB-IoT Module = 681 681 682 682 683 683 ((( 684 - (%style="color:blue"%)**Step2:**(%%) Openitandchoose731 +Users can directly access the AT command set of the NB-IoT module. 685 685 ))) 686 686 687 -* ((( 688 -Product Model 689 -))) 690 -* ((( 691 -Uplink Interval 692 -))) 693 -* ((( 694 -Working Mode 695 -))) 696 - 697 697 ((( 698 -And the Life expectation in difference case will be shown on the right. 699 -))) 735 +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/]] 700 700 701 -[[image:image-20220708141352-7.jpeg]] 702 - 703 - 704 - 705 -=== 2.9.3 Battery Note === 706 - 707 -((( 708 -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. 737 + 709 709 ))) 710 710 740 +[[image:1657333200519-600.png]] 711 711 712 712 713 -= ==2.9.4Replacethebattery===743 += 4. Using the AT Commands = 714 714 715 -((( 716 -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). 717 -))) 745 +== 4.1 Access AT Commands == 718 718 719 719 748 +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]] 720 720 721 -= 3. Access NB-IoT Module = 722 722 723 -((( 724 -Users can directly access the AT command set of the NB-IoT module. 725 -))) 751 +AT+<CMD>? : Help on <CMD> 726 726 727 -((( 728 -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/]] 729 -))) 753 +AT+<CMD> : Run <CMD> 730 730 731 - [[image:1657261278785-153.png]]755 +AT+<CMD>=<value> : Set the value 732 732 757 +AT+<CMD>=? : Get the value 733 733 734 734 735 - =4. UsingtheATCommands=760 +(% style="color:#037691" %)**General Commands**(%%) 736 736 737 - ==4.1AccessAT Commands==762 +AT : Attention 738 738 739 - Seethislinkfordetail:[[http:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/NSE01/>>url:http://www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN50/]]764 +AT? : Short Help 740 740 766 +ATZ : MCU Reset 741 741 742 -AT+ <CMD>?Helpon<CMD>768 +AT+TDC : Application Data Transmission Interval 743 743 744 -AT+ <CMD>Run<CMD>770 +AT+CFG : Print all configurations 745 745 746 -AT+ <CMD>=<value>: Setthevalue772 +AT+CFGMOD : Working mode selection 747 747 748 -AT+ <CMD>=?Get thevalue774 +AT+INTMOD : Set the trigger interrupt mode 749 749 776 +AT+5VT : Set extend the time of 5V power 750 750 751 - (%style="color:#037691"%)**GeneralCommands**(%%)778 +AT+PRO : Choose agreement 752 752 753 -AT : Attention780 +AT+WEIGRE : Get weight or set weight to 0 754 754 755 -AT ?: ShortHelp782 +AT+WEIGAP : Get or Set the GapValue of weight 756 756 757 -AT Z: MCU Reset784 +AT+RXDL : Extend the sending and receiving time 758 758 759 -AT+T DC: ApplicationData Transmission Interval786 +AT+CNTFAC : Get or set counting parameters 760 760 761 -AT+ CFGPrintall configurations788 +AT+SERVADDR : Server Address 762 762 763 -AT+ CFGMODWorkingmodeselection790 +AT+TR : Get or Set record time" 764 764 765 -AT+ INTMODSetthe triggerinterruptmode792 +AT+APN : Get or set the APN 766 766 767 -AT+ 5VT:Set extendthetimeof5V power794 +AT+FBAND : Get or Set whether to automatically modify the frequency band 768 768 769 -AT+ PRO: Chooseagreement796 +AT+DNSCFG : Get or Set DNS Server 770 770 771 -AT+ WEIGREGetweight or set weightto 0798 +AT+GETSENSORVALUE : Returns the current sensor measurement 772 772 773 -AT+ WEIGAP:Get or Set theGapValue ofweight800 +AT+NOUD : Get or Set the number of data to be uploaded 774 774 775 -AT+ RXDL: Extendthesendingandreceivingtime802 +AT+CDP : Read or Clear cached data 776 776 777 -AT+ CNTFACsetcounting parameters804 +AT+LDDSALARM : Get or Set alarm of distance 778 778 779 -AT+SERVADDR : Server Address 780 780 781 - 782 782 (% style="color:#037691" %)**COAP Management** 783 783 784 -AT+URI : Resource parameters 809 +AT+URI : Resource parameters 785 785 786 786 787 787 (% style="color:#037691" %)**UDP Management** 788 788 789 -AT+CFM : Upload confirmation mode (only valid for UDP) 814 +AT+CFM : Upload confirmation mode (only valid for UDP) 790 790 791 791 792 792 (% style="color:#037691" %)**MQTT Management** 793 793 794 -AT+CLIENT 819 +AT+CLIENT : Get or Set MQTT client 795 795 796 -AT+UNAME 821 +AT+UNAME : Get or Set MQTT Username 797 797 798 -AT+PWD 823 +AT+PWD : Get or Set MQTT password 799 799 800 -AT+PUBTOPIC 825 +AT+PUBTOPIC : Get or Set MQTT publish topic 801 801 802 -AT+SUBTOPIC 827 +AT+SUBTOPIC : Get or Set MQTT subscription topic 803 803 804 804 805 805 (% style="color:#037691" %)**Information** 806 806 807 -AT+FDR : Factory Data Reset 832 +AT+FDR : Factory Data Reset 808 808 809 -AT+PWORD : Serial Access Password 834 +AT+PWORD : Serial Access Password 810 810 811 811 812 - 813 813 = 5. FAQ = 814 814 815 815 == 5.1 How to Upgrade Firmware == ... ... @@ -824,18 +824,10 @@ 824 824 ))) 825 825 826 826 ((( 827 -(% style="color:red" %)Notice, NS E01and LSE01share the same mother board. They use the same connection and method to update.851 +(% style="color:red" %)**Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update.** 828 828 ))) 829 829 830 830 831 - 832 -== 5.2 Can I calibrate NSE01 to different soil types? == 833 - 834 -((( 835 -NSE01 is calibrated for saline-alkali soil and loamy soil. If users want to use it for other soil, they can calibrate the value in the IoT platform base on the value measured by saline-alkali soil and loamy soil. The formula can be found at [[this link>>https://www.dragino.com/downloads/downloads/LoRa_End_Node/LSE01/Calibrate_to_other_Soil_20220605.pdf]]. 836 -))) 837 - 838 - 839 839 = 6. Trouble Shooting = 840 840 841 841 == 6.1 Connection problem when uploading firmware == ... ... @@ -850,13 +850,11 @@ 850 850 851 851 ))) 852 852 853 - 854 854 == 6.2 AT Command input doesn't work == 855 855 871 + 856 856 ((( 857 857 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. 858 - 859 - 860 860 ))) 861 861 862 862 ... ... @@ -863,14 +863,9 @@ 863 863 = 7. Order Info = 864 864 865 865 866 -Part Number**:** (% style="color:#4f81bd" %)**NS E01**880 +Part Number**:** (% style="color:#4f81bd" %)**NSDDS75** 867 867 868 868 869 -(% class="wikigeneratedid" %) 870 -((( 871 - 872 -))) 873 - 874 874 = 8. Packing Info = 875 875 876 876 ((( ... ... @@ -878,7 +878,7 @@ 878 878 879 879 (% style="color:#037691" %)**Package Includes**: 880 880 881 -* NS E01NB-IoTSoil Moisture&ECSensor x 1890 +* NDDS75 NB-IoT Distance Detect Sensor Node x 1 882 882 * External antenna x 1 883 883 ))) 884 884 ... ... @@ -887,18 +887,20 @@ 887 887 888 888 (% style="color:#037691" %)**Dimension and weight**: 889 889 890 -* Size: 195 x 125 x 55 mm 891 -* 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 892 892 ))) 893 893 894 894 ((( 895 895 896 896 897 - 898 898 899 899 ))) 900 900 901 901 = 9. Support = 902 902 913 + 903 903 * 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. 904 904 * 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]]
- 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-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