Changes for page NSPH01-NB-IoT Soil pH Sensor User Manual
Last modified by Bei Jinggeng on 2024/03/30 17:53
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
-
Attachments (0 modified, 0 added, 3 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. Xiaoling1 +XWiki.Edwin - Content
-
... ... @@ -1,5 +1,5 @@ 1 1 (% style="text-align:center" %) 2 -[[image:)YK]Y_LZJIO]J2~~VA}OQJM2.png ||height="442" width="410"]]2 +[[image:)YK]Y_LZJIO]J2~~VA}OQJM2.png]] 3 3 4 4 **Table of Contents:** 5 5 ... ... @@ -7,33 +7,27 @@ 7 7 8 8 9 9 10 -= 1. 10 += 1. Introduction = 11 11 12 -== 1.1 12 +== 1.1 What is NSPH01 Soil pH Sensor == 13 13 14 +The Dragino NSPH01 is a **NB-IoT soil pH sensor** for IoT of Agriculture. It is designed to measure the soil pH and soil temperature, so to send to the platform to analyze the soil acid or alkali level. The probe is IP68 waterproof. 14 14 15 - The DraginoNSPH01is a (% style="color:blue"%)**NB-IoT soil pHsensor**(%%)forIoTofAgriculture. It is designedtomeasurethesoil pHandsoiltemperature,sotosendto theplatformtoanalyzethesoilacid or alkali level. The probeis IP68 waterproof.16 +NSPH01 probe is made by Solid AgCl reference electrode and Pure metal pH sensitive electrode. It can detect soil's** pH **with high accuracy and stable value. The NSPH01 probe can be buried into soil for long time use. 16 16 17 -NSPH01 probe is made by Solid AgCl reference electrode and Pure metal pH sensitive electrode. It can detect soil's** (% style="color:blue" %)pH (%%)**with high accuracy and stable value. The NSPH01 probe can be buried into soil for long time use. 18 - 19 19 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. 19 +\\NSPH01 supports different uplink methods include **TCP,MQTT,UDP and CoAP **for different application requirement. 20 +\\NSPH01 is powered by **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) 21 +\\To use NSPH01, user needs to check if there is NB-IoT coverage in the installation area and with the bands NSPH01 supports. If the local operator supports it, user needs to get a **NB-IoT SIM card** from local operator and install NSPH01 to get NB-IoT network connection. 20 20 21 -NSPH01 supports different uplink methods include (% style="color:blue" %)**TCP,MQTT,UDP and CoAP **(%%)for different application requirement. 22 - 23 -NSPH01 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) 24 - 25 -To use NSPH01, user needs to check if there is NB-IoT coverage in the installation area and with the bands NSPH01 supports. If the local operator supports it, user needs to get a (% style="color:blue" %)**NB-IoT SIM card** (%%)from local operator and install NSPH01 to get NB-IoT network connection. 26 - 27 - 23 +(% style="text-align:center" %) 28 28 [[image:image-20220907153151-1.png]] 29 29 30 - 26 +(% style="text-align:center" %) 31 31 [[image:M_K`YF9`CAYAE\@}3T]FHT$9.png]] 32 32 29 +== 1.2 Features == 33 33 34 -== 1.2 Features == 35 - 36 - 37 37 * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD 38 38 * Monitor soil pH with temperature compensation. 39 39 * Monitor soil temperature ... ... @@ -51,26 +51,24 @@ 51 51 52 52 == 1.3 Specification == 53 53 48 +**Common DC Characteristics:** 54 54 55 -(% style="color:#037691" %)**Common DC Characteristics:** 56 - 57 57 * Supply Voltage: 2.1v ~~ 3.6v 58 58 * Operating Temperature: -40 ~~ 85°C 59 59 60 - (% style="color:#037691" %)**NB-IoT Spec:**53 +**NB-IoT Spec:** 61 61 62 -* B1 @H-FDD: 2100MHz 63 -* B3 @H-FDD: 1800MHz 64 -* B8 @H-FDD: 900MHz 65 -* B5 @H-FDD: 850MHz 66 -* B20 @H-FDD: 800MHz 67 -* B28 @H-FDD: 700MHz 55 +* - B1 @H-FDD: 2100MHz 56 +* - B3 @H-FDD: 1800MHz 57 +* - B8 @H-FDD: 900MHz 58 +* - B5 @H-FDD: 850MHz 59 +* - B20 @H-FDD: 800MHz 60 +* - B28 @H-FDD: 700MHz 68 68 69 -== 1.4 62 +== 1.4 Probe Specification == 70 70 64 +**Soil pH:** 71 71 72 -(% style="color:#037691" %)**Soil pH:** 73 - 74 74 * Range: 3 ~~ 10 pH 75 75 * Resolution: 0.01 pH 76 76 * Accuracy: ±2% under (0~~50 ℃, Accuracy will poor under 0 due to frozen) ... ... @@ -78,7 +78,7 @@ 78 78 * IP68 Protection 79 79 * Length: 3.5 meters 80 80 81 - (% style="color:#037691" %)**Soil Temperature:**73 +**Soil Temperature:** 82 82 83 83 * Range -40℃~85℃ 84 84 * Resolution: 0.1℃ ... ... @@ -86,37 +86,31 @@ 86 86 * IP68 Protection 87 87 * Length: 3.5 meters 88 88 89 -== 1.5 81 +== 1.5 Applications == 90 90 91 - 92 92 * Smart Agriculture 93 93 94 -== 1.6 85 +== 1.6 Pin mapping and power on == 95 95 96 - 87 +(% style="text-align:center" %) 97 97 [[image:image-20220907153300-2.png]] 98 98 99 99 100 - 101 101 = 2. Use NSPH01 to communicate with IoT Server = 102 102 103 103 == 2.1 How it works == 104 104 105 - 106 106 The NSPH01 is equipped with a NB-IoT module, the pre-loaded firmware in NSPH01 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 NSPH01. 107 107 108 108 The diagram below shows the working flow in default firmware of NSPH01: 109 109 110 - 99 +(% style="text-align:center" %) 111 111 [[image:image-20220907153416-3.png]] 112 112 113 - 114 - 115 115 == 2.2 Configure the NSPH01 == 116 116 117 117 === 2.2.1 Test Requirement === 118 118 119 - 120 120 To use NSPH01 in the field, make sure meet below requirements: 121 121 122 122 * Your local operator has already distributed a NB-IoT Network there. ... ... @@ -123,204 +123,165 @@ 123 123 * The local NB-IoT network used the band that NSPH01 supports. 124 124 * Your operator is able to distribute the data received in their NB-IoT network to your IoT server. 125 125 126 -Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8. The NSPH01 will use **CoAP(120.24.4.116:5683)**or raw**UDP(120.24.4.116:5601)**or**MQTT(120.24.4.116:1883)**or**TCP(120.24.4.116:5600)**protocol to send data to the test server.112 +Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8. The NSPH01 will use CoAP(120.24.4.116:5683) or raw UDP(120.24.4.116:5601) or MQTT(120.24.4.116:1883)or TCP(120.24.4.116:5600)protocol to send data to the test server. 127 127 128 - 114 +(% style="text-align:center" %) 129 129 [[image:image-20220907153445-4.png]] 130 130 131 131 132 132 === 2.2.2 Insert SIM card === 133 133 134 - 135 135 User need to take out the NB-IoT module and insert the SIM card like below. ((% style="color:red" %) Pay attention to the direction(%%)) 136 136 137 - 122 +(% style="text-align:center" %) 138 138 [[image:image-20220907153505-5.png]] 139 139 140 - 141 141 === 2.2.3 Connect USB – TTL to NSPH01 to configure it === 142 142 127 +User need to configure NSPH01 via serial port to set the **Server Address** / **Uplink Topic** to define where and how-to uplink packets. NSPH01 support AT Commands, user can use a USB to TTL adapter to connect to NSPH01 and use AT Commands to configure it, as below. 143 143 144 - User need to configure NSPH01 via serial port to set the (% style="color:blue" %)**Server Address** / **Uplink Topic**(%%) to define where and how-to uplink packets. NSPH01 support ATCommands, user canusea USB to TTL adapter toconnectto NSPH01 and use AT Commands to configure it, as below.129 +**Connection:** 145 145 131 + USB TTL GND <~-~-~-~-> GND 146 146 147 - (%style="color:blue"%)**Connection:**133 + USB TTL TXD <~-~-~-~-> UART_RXD 148 148 149 - **~(% style="background-color:yellow" %)USB TTLGND <~-~-~-~->GND(%%)**135 + USB TTL RXD <~-~-~-~-> UART_TXD 150 150 151 -**~ (% style="background-color:yellow" %) USB TTL TXD <~-~-~-~-> UART_RXD(%%)** 152 - 153 -**~ (% style="background-color:yellow" %) USB TTL RXD <~-~-~-~-> UART_TXD(%%)** 154 - 155 - 156 156 In the PC, use below serial tool settings: 157 157 158 -* Baud: (% style="color:green" %)**9600**159 -* Data bits:** (% style="color:green" %)8(%%)**160 -* Stop bits: (% style="color:green" %)**1**161 -* Parity: (% style="color:green" %)**None**162 -* Flow Control: (%style="color:green" %)**None**139 +* Baud: **9600** 140 +* Data bits:** 8** 141 +* Stop bits: **1** 142 +* Parity: **None** 143 +* Flow Control: **None** 163 163 164 -Make sure the switch is in FLASH position, then power on device by connecting the jumper on NSPH01. NSPH01 will output system info once power on as below, we can enter the (% style="color:green" %)**password: 12345678**(%%)to access AT Command input.145 +Make sure the switch is in FLASH position, then power on device by connecting the jumper on NSPH01. NSPH01 will output system info once power on as below, we can enter the **password: 12345678** to access AT Command input. 165 165 147 +(% style="text-align:center" %) 148 +[[image:image-20220907153529-6.png]] 166 166 167 - [[image:image-20220912144017-1.png]]150 +**Note: the valid AT Commands can be found at: **[[**https:~~/~~/www.dropbox.com/sh/351dwor6joz8nwh/AADn1BQaAAxLF_QMyU8NkW47a?dl=0**>>url:https://www.dropbox.com/sh/351dwor6joz8nwh/AADn1BQaAAxLF_QMyU8NkW47a?dl=0]] 168 168 169 - 170 -(% style="color:red" %)**Note: the valid AT Commands can be found at:**(%%)** **[[**https:~~/~~/www.dropbox.com/sh/351dwor6joz8nwh/AADn1BQaAAxLF_QMyU8NkW47a?dl=0**>>url:https://www.dropbox.com/sh/351dwor6joz8nwh/AADn1BQaAAxLF_QMyU8NkW47a?dl=0]] 171 - 172 - 173 173 === 2.2.4 Use CoAP protocol to uplink data === 174 174 154 +**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/**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/]] 175 175 176 - (% style="color:red" %)**Note: if you don't have CoAPserver,you can refer thislink toset up one:**(%%)** **[[**http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/]]156 +**Use below commands:** 177 177 158 +* **AT+PRO=1** ~/~/ Set to use CoAP protocol to uplink 159 +* **AT+SERVADDR=120.24.4.116,5683 ** ~/~/ to set CoAP server address and port 160 +* **AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** ~/~/Set COAP resource path 178 178 179 -(% style="color:blue" %)**Use below commands:** 180 - 181 -* (% style="color:#037691" %)**AT+PRO=1** (%%) ~/~/ Set to use CoAP protocol to uplink 182 -* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5683 ** (%%) ~/~/ to set CoAP server address and port 183 -* (% style="color:#037691" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/ Set COAP resource path 184 - 185 185 For parameter description, please refer to AT command set 186 186 187 - 164 +(% style="text-align:center" %) 188 188 [[image:image-20220907153551-7.png||height="502" width="740"]] 189 189 167 +After configure the server address and **reset the device** (via AT+ATZ ), NSPH01 will start to uplink sensor values to CoAP server. 190 190 191 -After configure the server address and (% style="color:green" %)**reset the device (via AT+ATZ )**(%%), NSPH01 will start to uplink sensor values to CoAP server. 192 - 193 - 169 +(% style="text-align:center" %) 194 194 [[image:image-20220907153612-8.png||height="529" width="729"]] 195 195 196 196 197 197 === 2.2.5 Use UDP protocol to uplink data(Default protocol) === 198 198 199 - 200 200 This feature is supported since firmware version v1.0.1 201 201 202 -* (% style="color:blue" %)**AT+PRO=2 **(%%)~/~/203 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601 **(%%)~/~/204 -* (% style="color:blue" %)**AT+CFM=1 **(%%)~/~/177 +* **AT+PRO=2 ** ~/~/ Set to use UDP protocol to uplink 178 +* **AT+SERVADDR=120.24.4.116,5601 ** ~/~/ to set UDP server address and port 179 +* **AT+CFM=1 ** ~/~/If the server does not respond, this command is unnecessar 205 205 181 +(% style="text-align:center" %) 206 206 [[image:image-20220907153643-9.png||height="401" width="734"]] 207 207 208 - 184 +(% style="text-align:center" %) 209 209 [[image:image-20220907153703-10.png||height="309" width="738"]] 210 210 211 211 212 212 === 2.2.6 Use MQTT protocol to uplink data === 213 213 214 - 215 215 This feature is supported since firmware version v110 216 216 217 -* (% style="color:blue" %)**AT+PRO=3 **(%%)~/~/218 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883 **(%%)~/~/219 -* (% style="color:blue" %)**AT+CLIENT=CLIENT **(%%)~/~/220 -* (% style="color:blue" %)**AT+UNAME=UNAME **(%%)~/~/221 -* (% style="color:blue" %)**AT+PWD=PWD **(%%)~/~/222 -* (% style="color:blue" %)**AT+PUBTOPIC=NSE01_PUB **(%%)~/~/223 -* (% style="color:blue" %)**AT+SUBTOPIC=NSE01_SUB **(%%)~/~/192 +* **AT+PRO=3 ** ~/~/Set to use MQTT protocol to uplink 193 +* **AT+SERVADDR=120.24.4.116,1883 ** ~/~/Set MQTT server address and port 194 +* **AT+CLIENT=CLIENT ** ~/~/Set up the CLIENT of MQTT 195 +* **AT+UNAME=UNAME **~/~/Set the username of MQTT 196 +* **AT+PWD=PWD **~/~/Set the password of MQTT 197 +* **AT+PUBTOPIC=NSE01_PUB **~/~/Set the sending topic of MQTT 198 +* **AT+SUBTOPIC=NSE01_SUB ** ~/~/Set the subscription topic of MQTT 224 224 200 +(% style="text-align:center" %) 225 225 [[image:image-20220907153739-11.png||height="491" width="764"]] 226 226 227 - 203 +(% style="text-align:center" %) 228 228 [[image:image-20220907153751-12.png||height="555" width="769"]] 229 229 230 - 231 231 MQTT protocol has a much higher power consumption compare vs UDP / CoAP protocol. Please check the power analyze document and adjust the uplink period to a suitable interval. 232 232 233 - 234 234 === 2.2.7 Use TCP protocol to uplink data === 235 235 236 - 237 237 This feature is supported since firmware version v110 238 238 239 -* (% style="color:blue" %)**AT+PRO=4 **(%%)~/~/ Set to use TCP protocol to uplink240 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600 **(%%)~/~/ to set TCP server address and port212 +* **AT+PRO=4 ** ~/~/ Set to use TCP protocol to uplink 213 +* **AT+SERVADDR=120.24.4.116,5600 ** ~/~/ to set TCP server address and port 241 241 215 +(% style="text-align:center" %) 242 242 [[image:image-20220907153818-13.png||height="486" width="668"]] 243 243 244 - 218 +(% style="text-align:center" %) 245 245 [[image:image-20220907153827-14.png||height="236" width="684"]] 246 246 247 - 248 248 === 2.2.8 Change Update Interval === 249 249 250 - 251 251 Users can use the below command to change the **uplink interval**. 252 252 253 -* (% style="color:blue" %)**AT+TDC=7200 **(%%)~/~/ Set Update Interval to 7200s (2 hour)225 +* **AT+TDC=7200 ** ~/~/ Set Update Interval to 7200s (2 hour) 254 254 255 -(% style="color:red" %)**NOTE: 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).** 256 256 228 +**NOTE: 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).** 257 257 230 + 258 258 == 2.3 Uplink Payload == 259 259 260 - 261 261 In this mode, uplink payload includes 87 bytes in total by default. 262 262 263 263 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. 264 264 265 -(% border="1.5" style="background-color:#ffffcc; color:green; width:520px" %) 266 -|=(% scope="row" style="width: 50px;" %)**Size(bytes)**|(% style="width:40px" %)**8**|(% style="width:20px" %)**2**|(% style="width:25px" %)**2**|(% style="width:60px" %)**1**|(% style="width:20px" %)**1**|(% style="width:40px" %)**1**|(% style="width:40px" %)**2**|(% style="width:50px" %)**2**|(% style="width:50px" %)**4**|(% style="width:50px" %)**2**|(% style="width:35px" %)**2**|(% style="width:40px" %)**4** 267 -|=(% style="width: 96px;" %)**Value**|(% style="width:83px" %)Device ID|(% style="width:44px" %)Ver|(% style="width:42px" %)BAT|(% style="width:124px" %)Signal Strength|(% style="width:57px" %)MOD|(% style="width:80px" %)Interrupt|(% style="width:69px" %)Soil PH|(% style="width:134px" %)Soil Temperature|(% style="width:98px" %)Time stamp|(% style="width:134px" %)Soil Temperature|(% style="width:68px" %)Soil PH|(% style="width:125px" %)Time stamp ..... 237 +|**Size(bytes)**|**8**|**2**|**2**|1|1|1|2|2|4|2|2|4 238 +|**Value**|Device ID|Ver|BAT|Signal Strength|MOD|Interrupt|Soil PH|Soil Temperature|Time stamp|Soil Temperature|Soil PH|Time stamp ..... 268 268 269 269 If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NSPH01 uplink data. 270 270 242 +(% style="text-align:center" %) 271 271 [[image:image-20220907153902-15.png||height="581" width="804"]] 272 272 273 273 274 -((( 275 275 The payload is ASCII string, representative same HEX: 276 -))) 277 277 278 -((( 279 - 280 -))) 248 +0xf86841105675413800640c781701000225010b6315537b010b0226631550fb010e022663154d7701110225631549f1011502246315466b01190223631542e5011d022163153f62011e022163153bde011e022163153859 where: 281 281 282 -((( 283 -**0x (% style="color:red" %)__f868411056754138__ (% style="color:blue" %)__0064 __ (% style="color:green" %)__0c78__ (% style="color:#00b0f0" %)__17__ (% style="color:#7030a0" %)__01__ (% style="color:#d60093" %)__00__ (% style="color:#a14d07" %)__0225 __ (% style="color:#0020b0" %) __010b__ (% style="color:#420042" %)__6315537b__ (% style="color:#663300" %)//__010b0226631550fb__ __010e022663154d77 01110225631549f1 011502246315466b 01190223631542e5 011d022163153f62 011e022163153bde 011e022163153859__//(%%)** 284 -))) 250 +* Device ID: 0xf868411056754138 = f868411056754138 251 +* Version: 0x0064=100=1.0.0 285 285 286 -((( 287 - 253 +* BAT: 0x0c78 = 3192 mV = 3.192V 254 +* Singal: 0x17 = 23 255 +* Mod: 0x01 = 1 256 +* Interrupt: 0x00= 0 257 +* Soil PH: 0x0225= 549 = 5.49 258 +* Soil Temperature:0x010B =267=26.7 °C 259 +* Time stamp : 0x6315537b =1662342011 260 +* Soil Temperature,Soil PH,Time stamp : 010b0226631550fb 261 +* 8 sets of recorded data: Temperature,Soil PH,Time stamp : 010e022663154d77,....... 288 288 289 -**where:** 290 -))) 291 - 292 -* (% style="color:#037691" %)**Device ID:**(%%)** **0xf868411056754138 = f868411056754138 293 - 294 -* (% style="color:#037691" %)**Version:** (%%) 0x0064=100=1.0.0 295 - 296 -* (% style="color:#037691" %)**BAT:** (%%) 0x0c78 = 3192 mV = 3.192V 297 - 298 -* (% style="color:#037691" %)**Singal:** (%%)0x17 = 23 299 - 300 -* (% style="color:#037691" %)**Mod:** (%%) 0x01 = 1 301 - 302 -* (% style="color:#037691" %)**Interrupt:**(%%) 0x00= 0 303 - 304 -* (% style="color:#037691" %)**Soil PH:** (%%) 0x0225= 549 = 5.49 305 - 306 -* (% style="color:#037691" %)**Soil Temperature:**(%%) 0x010b =267=26.7 °C 307 - 308 -* (% style="color:#037691" %)**Time stamp :** (%%) 0x6315537b =1662342011 ([[Unix Epoch Time>>url:http://www.epochconverter.com/]]) 309 - 310 -* (% style="color:#037691" %)**Soil Temperature,Soil PH,Time stamp : **(%%) 010b0226631550fb 311 - 312 -* (% style="color:#037691" %)**8 sets of recorded data:**(%%) Temperature,Soil PH,Time stamp : 010e022663154d77,....... 313 - 314 314 == 2.4 Payload Explanation and Sensor Interface == 315 315 316 316 === 2.4.1 Device ID === 317 317 318 - 319 319 By default, the Device ID equal to the last 15 bits of IMEI. 320 320 321 -User can use (% style="color:blue" %)**AT+DEUI**(%%)to set Device ID269 +User can use **AT+DEUI** to set Device ID 322 322 323 - 324 324 **Example:** 325 325 326 326 AT+DEUI=868411056754138 ... ... @@ -327,18 +327,14 @@ 327 327 328 328 The Device ID is stored in a none-erase area, Upgrade the firmware or run AT+FDR won't erase Device ID. 329 329 330 - 331 331 === 2.4.2 Version Info === 332 332 333 - 334 334 Specify the software version: 0x64=100, means firmware version 1.00. 335 335 336 336 For example: 0x00 64 : this device is NSPH01 with firmware version 1.0.0. 337 337 338 - 339 339 === 2.4.3 Battery Info === 340 340 341 - 342 342 Check the battery voltage for NSPH01. 343 343 344 344 Ex1: 0x0B45 = 2885mV ... ... @@ -345,10 +345,8 @@ 345 345 346 346 Ex2: 0x0B49 = 2889mV 347 347 348 - 349 349 === 2.4.4 Signal Strength === 350 350 351 - 352 352 NB-IoT Network signal Strength. 353 353 354 354 **Ex1: 0x1d = 29** ... ... @@ -363,23 +363,18 @@ 363 363 364 364 **99** Not known or not detectable 365 365 366 - 367 367 === 2.4.5 Soil PH === 368 368 369 - 370 370 Get the PH content of the soil. The value range of the register is 300-1000(Decimal), divide this value by 100 to get the percentage of PH in the soil. 371 371 372 -For example, if the data you get from the register is (% style="color:blue" %)**__0x05 0xDC__**(%%), the PH content in the soil is311 +For example, if the data you get from the register is **__0x05 0xDC__**, the PH content in the soil is 373 373 374 - (% style="color:blue" %)**0229(H) = 549(D) /100 = 5.49.**313 +**0229(H) = 549(D) /100 = 5.49.** 375 375 376 - 377 377 === 2.4.6 Soil Temperature === 378 378 317 +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 379 379 380 -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 (% style="color:blue" %)**__0x09 0xEC__**(%%), the temperature content in the soil is 381 - 382 - 383 383 **Example**: 384 384 385 385 If payload is 0105H: ((0x0105 & 0x8000)>>15 === 0),temp = 0105(H)/10 = 26.1 °C ... ... @@ -386,42 +386,35 @@ 386 386 387 387 If payload is FF7EH: ((FF7E & 0x8000)>>15 ===1),temp = (FF7E(H)-FFFF(H))/10 = -12.9 °C 388 388 389 - 390 390 === 2.4.7 Timestamp === 391 391 392 - 393 393 Time stamp : 0x6315537b =1662342011 394 394 395 395 Convert Unix timestamp to time 2022-9-5 9:40:11. 396 396 397 - 398 398 === 2.4.8 Digital Interrupt === 399 399 333 +Digital Interrupt refers to pin **GPIO_EXTI**, and there are different trigger methods. When there is a trigger, the NSPH01 will send a packet to the server. 400 400 401 -Digital Interrupt refers to pin (% style="color:blue" %)**GPIO_EXTI**(%%), and there are different trigger methods. When there is a trigger, the NSPH01 will send a packet to the server. 402 - 403 403 The command is: 404 404 405 - (% 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]])**.**337 +**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]])**.** 406 406 407 407 The lower four bits of this data field shows if this packet is generated by interrupt or not. Click here for the hardware and software set up. 408 408 341 +Example: 409 409 410 -**Example:** 411 - 412 412 0x(00): Normal uplink packet. 413 413 414 414 0x(01): Interrupt Uplink Packet. 415 415 416 - 417 417 === 2.4.9 +5V Output === 418 418 419 - 420 420 NSPH01 will enable +5V output before all sampling and disable the +5v after all sampling. 421 421 422 422 The 5V output time can be controlled by AT Command. 423 423 424 - (% style="color:blue" %)**AT+5VT=1000**353 +**AT+5VT=1000** 425 425 426 426 Means set 5V valid time to have 1000ms. So the real 5V output will actually have 1000ms + sampling time for other sensors.** ** 427 427 ... ... @@ -428,16 +428,21 @@ 428 428 429 429 == 2.5 Downlink Payload == 430 430 431 - 432 432 By default, NSPH01 prints the downlink payload to console port. 433 433 362 +(% style="text-align:center" %) 434 434 [[image:image-20220907154636-17.png]] 435 435 436 436 437 -(% style="color:blue" %)**Examples:** 438 438 439 -* (% style="color:#037691" %)** Set TDC** 440 440 368 + 369 + 370 + 371 +**Examples:** 372 + 373 +* **Set TDC** 374 + 441 441 If the payload=0100003C, it means set the END Node's TDC to 0x00003C=60(S), while type code is 01. 442 442 443 443 Payload: 01 00 00 1E TDC=30S ... ... @@ -444,18 +444,16 @@ 444 444 445 445 Payload: 01 00 00 3C TDC=60S 446 446 447 -* (% style="color:#037691" %)**381 +* **Reset** 448 448 449 449 If payload = 0x04FF, it will reset the NSPH01 450 450 451 -* (% style="color:#037691" %)**385 +* **INTMOD** 452 452 453 453 Downlink Payload: 06000003, Set AT+INTMOD=3 454 454 455 - 456 456 == 2.6 LED Indicator == 457 457 458 - 459 459 The NSPH01 has an internal LED which is to show the status of different state. 460 460 461 461 * When power on, NSPH01 will detect if sensor probe is connected, if probe detected, LED will blink four times. (no blinks in this step is no probe) ... ... @@ -463,20 +463,16 @@ 463 463 * After NSPH01 join NB-IoT network. The LED will be ON for 3 seconds. 464 464 * For each uplink probe, LED will be on for 500ms. 465 465 466 -== 2.7 398 +== 2.7 Installation and Maintain == 467 467 468 -=== 2.7.1 400 +=== 2.7.1 Before measurement === 469 469 470 - 471 471 If the NSPH01 has more than 7 days not use or just clean the pH probe. User should put the probe inside pure water for more than 24 hours for activation. If no put in water, user need to put inside soil for more than 24 hours to ensure the measurement accuracy. 472 472 404 +=== 2.7.2 Measurement === 473 473 474 - === 2.7.2Measurement===406 +**Measurement the soil surface:** 475 475 476 - 477 -(% style="color:#037691" %)**Measurement the soil surface:** 478 - 479 - 480 480 [[image:image-20220907154700-18.png]] 481 481 482 482 Choose the proper measuring position. Split the surface soil according to the measured deep. ... ... @@ -487,17 +487,14 @@ 487 487 488 488 Put soil over the probe after insert. And start to measure. 489 489 418 +**Measurement inside soil:** 490 490 491 -(% style="color:#037691" %)**Measurement inside soil:** 492 - 493 493 Dig a hole with diameter > 20CM. 494 494 495 495 Insert the probe inside, method like measure the surface. 496 496 424 +=== 2.7.3 Maintain Probe === 497 497 498 -=== 2.7.3 Maintain Probe === 499 - 500 - 501 501 1. pH probe electrode is fragile and no strong. User must avoid strong force or hitting it. 502 502 1. After long time use (3~~ 6 months). The probe electrode needs to be clean; user can use high grade sandpaper to polish it or put in 5% hydrochloric acid for several minutes. After the metal probe looks like new, user can use pure water to wash it. 503 503 1. Probe reference electrode is also no strong, need to avoid strong force or hitting. ... ... @@ -505,13 +505,12 @@ 505 505 1. Avoid the probes to touch oily matter. Which will cause issue in accuracy. 506 506 1. The probe is IP68 can be put in water. 507 507 508 -== 2.8 433 +== 2.8 PH and Temperature alarm function == 509 509 435 +➢ AT Command: 510 510 511 - (% style="color:#037691" %)**➢ATCommand:**437 +AT+ PHALARM=min,max 512 512 513 -(% style="color:blue" %)**AT+ PHALARM=min,max** 514 - 515 515 ² When min=3, and max≠0, Alarm higher than max 516 516 517 517 ² When min≠0, and max=0, Alarm lower than min ... ... @@ -518,11 +518,10 @@ 518 518 519 519 ² When min≠0 and max≠0, Alarm higher than max or lower than min 520 520 445 +Example: 521 521 522 - (%style="color:blue"%)**Example:**447 +AT+ PHALARM =5,8 ~/~/ Alarm when PH lower than 5. 523 523 524 -AT+ PHALARM =5,8 ~/~/ Alarm when PH lower than 5. 525 - 526 526 AT+ TEMPALARM=min,max 527 527 528 528 ² When min=0, and max≠0, Alarm higher than max ... ... @@ -531,71 +531,98 @@ 531 531 532 532 ² When min≠0 and max≠0, Alarm higher than max or lower than min 533 533 457 +Example: 534 534 535 - (%style="color:blue"%)**Example:**459 +AT+ TEMPALARM=20,30 ~/~/ Alarm when temperature lower than 20. 536 536 537 -AT+ TEMPALARM=20,30 ~/~/ Alarm when temperature lower than 20. 538 538 462 +== 2.9 Set the number of data to be uploaded and the recording time == 539 539 540 - ==2.9Set the numberof data to be uploaded andthe recording time ==464 +➢ AT Command: 541 541 466 +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) 542 542 543 - (%style="color:#037691"%)**➢ATCommand:**468 +AT+NOUD=8 ~/~/The device uploads 8 sets of recorded data by default. Up to 32 sets of record data can be uploaded. 544 544 545 -* (% style="color:blue" %)**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) 546 -* (% style="color:blue" %)**AT+NOUD=8** (%%) ~/~/ The device uploads 8 sets of recorded data by default. Up to 32 sets of record data can be uploaded. 547 547 548 - Thediagrambelowexplainstherelationship between TR, NOUD,andTDC more clearly**:**471 +== 2.10 Read or Clear cached data == 549 549 550 - [[image:image-20221009000933-1.png||height="750" width="1043"]]473 +➢ AT Command: 551 551 475 +AT+CDP ~/~/ Read cached data 552 552 553 - == 2.10 Read or Clear cached data ==477 +[[image:image-20220907154700-19.png]] 554 554 555 555 556 - (% style="color:#037691"%)**➢ATCommand:**480 +AT+CDP=0 ~/~/ Clear cached data 557 557 558 -* (% style="color:blue" %)**AT+CDP** (%%) ~/~/ Read cached data 559 -* (% style="color:blue" %)**AT+CDP=0** (%%) ~/~/ Clear cached data 560 560 561 - [[image:image-20220907154700-19.png]]483 +== 2.11 Calibration == 562 562 485 +User can do calibration for the probe. It is limited to use below pH buffer solution to calibrate: 4.00, 6.86, 9.18. When calibration, user need to clean the electrode and put the probe in the pH buffer solution to wait the value stable ( a new clean electrode might need max 24 hours to be stable). 563 563 564 - ==2.11Calibration ==487 +After stable, user can use below command to calibrate. 565 565 489 +[[image:image-20220907154700-20.png]] 566 566 567 - Usercan do calibration for the probe.Itis limited to use belowpH buffer solution to calibrate:4.00, 6.86, 9.18. When calibration, userneed toclean the electrode and put the probe in the pH buffer solution to wait the value stable ( a new clean electrode mightneed max 24 hours to be stable).491 +== 2.12 Firmware Change Log == 568 568 569 - Afterstable,user canusebelowlibrate.493 +Download URL & Firmware Change log: [[https:~~/~~/www.dropbox.com/sh/1zmcakvbkf24f8x/AACmq2dZ3iRB9F1nVWeEB9Moa?dl=0>>url:https://www.dropbox.com/sh/1zmcakvbkf24f8x/AACmq2dZ3iRB9F1nVWeEB9Moa?dl=0]] 570 570 495 +Upgrade Instruction: [[Upgrade Firmware>>path:#H5.1200BHowtoUpgradeFirmware]] 571 571 572 - [[image:image-20220907154700-20.png]]497 +== 2.13 Battery Analysis == 573 573 499 +=== 2.13.1 Battery Type === 574 574 575 - ==2.12Firmware ChangeLog==501 +The NSPH01 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. 576 576 503 +The battery is designed to last for several years depends on the actually use environment and update interval. 577 577 578 - Download URL & Firmware Changelog: [[https:~~/~~/www.dropbox.com/sh/1tv07fro2pvjqj8/AAD-2wbfGfluTZfh38fQqdA_a?dl=0>>https://www.dropbox.com/sh/1tv07fro2pvjqj8/AAD-2wbfGfluTZfh38fQqdA_a?dl=0]]505 +The battery-related documents as below: 579 579 580 -Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]] 507 +* [[Battery Dimension>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 508 +* [[Lithium-Thionyl Chloride Battery datasheet>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 509 +* [[Lithium-ion Battery-Capacitor datasheet>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 581 581 511 +[[image:image-20220907154700-21.png]] 582 582 583 -== 2.13 Battery &PowerConsumption ==513 +=== 2.13.2 Power consumption Analyze === 584 584 515 +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. 585 585 586 - NSPH01 uses ER26500 + SPC1520 battery pack. See below link for detail informationaboutthebatteryinfo and how to replace.517 +Instruction to use as below: 587 587 588 - [[**BatteryInfo& PowerConsumption**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20calculate%20the%20battery%20life%20of%20Dragino%20sensors%3F/]].519 +**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/]] 589 589 521 +**Step 2: ** Open it and choose 590 590 591 -= 3. Access NB-IoT Module = 523 +* Product Model 524 +* Uplink Interval 525 +* Working Mode 592 592 527 +And the Life expectation in difference case will be shown on the right. 593 593 529 +(% style="text-align:center" %) 530 +[[image:image-20220907154700-22.jpeg]] 531 + 532 + 533 + 534 +=== 2.13.3 Battery Note === 535 + 536 +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. 537 + 538 +=== 2.13.4 Replace the battery === 539 + 540 +The default battery pack of NSPH01 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). 541 + 542 += 3. Access NB-IoT Module = 543 + 594 594 Users can directly access the AT command set of the NB-IoT module. 595 595 596 596 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/]] 597 597 598 - 548 +(% style="text-align:center" %) 599 599 [[image:image-20220907154700-23.png]] 600 600 601 601 ... ... @@ -604,7 +604,6 @@ 604 604 605 605 == 4.1 Access AT Commands == 606 606 607 - 608 608 See this link for detail: [[https:~~/~~/www.dropbox.com/sh/351dwor6joz8nwh/AADn1BQaAAxLF_QMyU8NkW47a?dl=0>>url:https://www.dropbox.com/sh/351dwor6joz8nwh/AADn1BQaAAxLF_QMyU8NkW47a?dl=0]] 609 609 610 610 AT+<CMD>? : Help on <CMD> ... ... @@ -615,9 +615,8 @@ 615 615 616 616 AT+<CMD>=? : Get the value 617 617 567 +**General Commands** 618 618 619 -(% style="color:#037691" %)**General Commands** 620 - 621 621 AT : Attention 622 622 623 623 AT? : Short Help ... ... @@ -642,18 +642,13 @@ 642 642 643 643 AT+TR : Get or Set record time" 644 644 645 -AT+APN : Get or set the APN 646 646 647 -AT+FBAND : Get or Set whether to automatically modify the frequency band 648 - 649 -AT+DNSCFG : Get or Set DNS Server 650 - 651 -AT+GETSENSORVALUE : Returns the current sensor measurement 652 - 653 653 AT+NOUD : Get or Set the number of data to be uploaded 654 654 596 + 655 655 AT+CDP : Read or Clear cached data 656 656 599 + 657 657 AT+TEMPALARM : Get or Set alarm of temp 658 658 659 659 AT+PHALARM : Get or Set alarm of PH ... ... @@ -661,18 +661,16 @@ 661 661 AT+ PHCAL : calibrate PH value 662 662 663 663 664 - (% style="color:#037691" %)**COAP Management**607 +**COAP Management** 665 665 666 666 AT+URI : Resource parameters 667 667 611 +**UDP Management** 668 668 669 -(% style="color:#037691" %)**UDP Management** 670 - 671 671 AT+CFM : Upload confirmation mode (only valid for UDP) 672 672 615 +**MQTT Management** 673 673 674 -(% style="color:#037691" %)**MQTT Management** 675 - 676 676 AT+CLIENT : Get or Set MQTT client 677 677 678 678 AT+UNAME : Get or Set MQTT Username ... ... @@ -683,56 +683,42 @@ 683 683 684 684 AT+SUBTOPIC : Get or Set MQTT subscription topic 685 685 627 +**Information** 686 686 687 -(% style="color:#037691" %)**Information** 688 - 689 689 AT+FDR : Factory Data Reset 690 690 691 691 AT+PWORD : Serial Access Password 692 692 693 - 694 694 = 5. FAQ = 695 695 696 696 == 5.1 How to Upgrade Firmware == 697 697 698 - 699 699 User can upgrade the firmware for 1) bug fix, 2) new feature release. 700 700 701 701 Please see this link for how to upgrade: [[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Firmware%20Upgrade%20Instruction%20for%20STM32%20base%20products/#H2.HardwareUpgradeMethodSupportList>>url:http://wiki.dragino.com/xwiki/bin/view/Main/Firmware%20Upgrade%20Instruction%20for%20STM32%20base%20products/#H2.HardwareUpgradeMethodSupportList]] 702 702 703 - (% style="color:red" %)**Notice, NSPH01 andLSPH01 share the same mother board. They use the same connection and method to update.**641 +**Notice, **NSPH01 **and **NSPH01 **share the same mother board. They use the same connection and method to update.** 704 704 705 - 706 706 == 5.2 Can I calibrate NSPH01 to different soil types? == 707 707 708 - 709 709 NSPH01 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>>url:https://www.dragino.com/downloads/downloads/LoRa_End_Node/LSE01/Calibrate_to_other_Soil_20220605.pdf]]. 710 710 711 - 712 712 = 6. Trouble Shooting = 713 713 714 714 == 6.1 Connection problem when uploading firmware == 715 715 716 - 717 717 **Please see: **[[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Firmware%20Upgrade%20Instruction%20for%20STM32%20base%20products/#H3.3Troubleshooting>>url:http://wiki.dragino.com/xwiki/bin/view/Main/Firmware%20Upgrade%20Instruction%20for%20STM32%20base%20products/#H3.3Troubleshooting]] 718 718 719 - 720 720 == 6.2 AT Command input doesn't work == 721 721 655 +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 **ENTER** while sending out the command. Some serial tool doesn't send **ENTER** while press the send key, user need to add ENTER in their string. 722 722 723 -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. 724 - 725 - 726 726 = 7. Order Info = 727 727 728 - 729 729 Part Number**:** NSPH01 730 730 731 - 732 - 733 733 = 8. Packing Info = 734 734 735 - 736 736 **Package Includes**: 737 737 738 738 * NSPH01 NB-IoT pH Sensor x 1 ... ... @@ -740,14 +740,11 @@ 740 740 741 741 **Dimension and weight**: 742 742 743 -* Device Size: cm 744 -* Device Weight: g 745 -* Package Size / pcs : cm 746 -* Weight / pcs : g 670 +* Size: 195 x 125 x 55 mm 671 +* Weight: 420g 747 747 748 748 = 9. Support = 749 749 750 - 751 751 * 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. 752 752 * 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]] 753 753
- image-20220912144017-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -149.6 KB - Content
- image-20220923101327-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -12.1 KB - Content
- image-20221009000933-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Edwin - Size
-
... ... @@ -1,1 +1,0 @@ 1 -282.9 KB - Content