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, 2 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. Edwin1 +XWiki.David - 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,32 +7,27 @@ 7 7 8 8 9 9 10 -= 1. 10 += 1. Introduction = 11 11 12 +== 1.1 What is NSPH01 Soil pH Sensor == 12 12 13 - == 1.1 WhatisNSPH01Soil pHSensor==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 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. 15 15 16 -The Dragino NSPH01 is a (% style="color:blue" %)**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. 17 - 18 -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. 19 - 20 20 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. 21 -\\NSPH01 supports different uplink methods include (% style="color:blue" %)**TCP,MQTT,UDP and CoAP **(%%)for different application requirement.22 -\\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)23 -\\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.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. 24 24 25 - 23 +(% style="text-align:center" %) 26 26 [[image:image-20220907153151-1.png]] 27 27 28 - 26 +(% style="text-align:center" %) 29 29 [[image:M_K`YF9`CAYAE\@}3T]FHT$9.png]] 30 30 29 +== 1.2 Features == 31 31 32 - 33 -== 1.2 Features == 34 - 35 - 36 36 * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD 37 37 * Monitor soil pH with temperature compensation. 38 38 * Monitor soil temperature ... ... @@ -50,13 +50,12 @@ 50 50 51 51 == 1.3 Specification == 52 52 48 +**Common DC Characteristics:** 53 53 54 -(% style="color:#037691" %)**Common DC Characteristics:** 55 - 56 56 * Supply Voltage: 2.1v ~~ 3.6v 57 57 * Operating Temperature: -40 ~~ 85°C 58 58 59 - (% style="color:#037691" %)**NB-IoT Spec:**53 +**NB-IoT Spec:** 60 60 61 61 * - B1 @H-FDD: 2100MHz 62 62 * - B3 @H-FDD: 1800MHz ... ... @@ -65,11 +65,10 @@ 65 65 * - B20 @H-FDD: 800MHz 66 66 * - B28 @H-FDD: 700MHz 67 67 68 -== 1.4 62 +== 1.4 Probe Specification == 69 69 64 +**Soil pH:** 70 70 71 -(% style="color:#037691" %)**Soil pH:** 72 - 73 73 * Range: 3 ~~ 10 pH 74 74 * Resolution: 0.01 pH 75 75 * Accuracy: ±2% under (0~~50 ℃, Accuracy will poor under 0 due to frozen) ... ... @@ -77,7 +77,7 @@ 77 77 * IP68 Protection 78 78 * Length: 3.5 meters 79 79 80 - (% style="color:#037691" %)**Soil Temperature:**73 +**Soil Temperature:** 81 81 82 82 * Range -40℃~85℃ 83 83 * Resolution: 0.1℃ ... ... @@ -85,39 +85,31 @@ 85 85 * IP68 Protection 86 86 * Length: 3.5 meters 87 87 88 -== 1.5 81 +== 1.5 Applications == 89 89 90 - 91 91 * Smart Agriculture 92 92 93 -== 1.6 85 +== 1.6 Pin mapping and power on == 94 94 95 - 87 +(% style="text-align:center" %) 96 96 [[image:image-20220907153300-2.png]] 97 97 98 98 99 - 100 100 = 2. Use NSPH01 to communicate with IoT Server = 101 101 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 - 118 118 === 2.2.1 Test Requirement === 119 119 120 - 121 121 To use NSPH01 in the field, make sure meet below requirements: 122 122 123 123 * Your local operator has already distributed a NB-IoT Network there. ... ... @@ -124,205 +124,163 @@ 124 124 * The local NB-IoT network used the band that NSPH01 supports. 125 125 * Your operator is able to distribute the data received in their NB-IoT network to your IoT server. 126 126 127 -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. 128 128 129 - 114 +(% style="text-align:center" %) 130 130 [[image:image-20220907153445-4.png]] 131 131 132 132 133 - 134 134 === 2.2.2 Insert SIM card === 135 135 136 - 137 137 User need to take out the NB-IoT module and insert the SIM card like below. ((% style="color:red" %) Pay attention to the direction(%%)) 138 138 139 - 122 +(% style="text-align:center" %) 140 140 [[image:image-20220907153505-5.png]] 141 141 142 - 143 - 144 144 === 2.2.3 Connect USB – TTL to NSPH01 to configure it === 145 145 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. 146 146 147 - 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:** 148 148 131 + USB TTL GND <~-~-~-~-> GND 149 149 150 - (%style="color:blue"%)**Connection:**133 + USB TTL TXD <~-~-~-~-> UART_RXD 151 151 152 - **~(% style="background-color:yellow" %)USB TTLGND <~-~-~-~->GND(%%)**135 + USB TTL RXD <~-~-~-~-> UART_TXD 153 153 154 -**~ (% style="background-color:yellow" %) USB TTL TXD <~-~-~-~-> UART_RXD(%%)** 155 - 156 -**~ (% style="background-color:yellow" %) USB TTL RXD <~-~-~-~-> UART_TXD(%%)** 157 - 158 - 159 159 In the PC, use below serial tool settings: 160 160 161 -* Baud: (% style="color:green" %)**9600**162 -* Data bits:** (% style="color:green" %)8(%%)**163 -* Stop bits: (% style="color:green" %)**1**164 -* Parity: (% style="color:green" %)**None**165 -* Flow Control: (%style="color:green" %)**None**139 +* Baud: **9600** 140 +* Data bits:** 8** 141 +* Stop bits: **1** 142 +* Parity: **None** 143 +* Flow Control: **None** 166 166 167 -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. 168 168 147 +(% style="text-align:center" %) 148 +[[image:image-20220907153529-6.png]] 169 169 170 - [[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]] 171 171 172 - 173 -(% 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]] 174 - 175 - 176 - 177 177 === 2.2.4 Use CoAP protocol to uplink data === 178 178 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/]] 179 179 180 - (% 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:** 181 181 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 182 182 183 -(% style="color:blue" %)**Use below commands:** 184 - 185 -* (% style="color:#037691" %)**AT+PRO=1** (%%) ~/~/ Set to use CoAP protocol to uplink 186 -* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5683 ** (%%) ~/~/ to set CoAP server address and port 187 -* (% style="color:#037691" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/ Set COAP resource path 188 - 189 189 For parameter description, please refer to AT command set 190 190 191 - 164 +(% style="text-align:center" %) 192 192 [[image:image-20220907153551-7.png||height="502" width="740"]] 193 193 167 +After configure the server address and **reset the device** (via AT+ATZ ), NSPH01 will start to uplink sensor values to CoAP server. 194 194 195 -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. 196 - 197 - 169 +(% style="text-align:center" %) 198 198 [[image:image-20220907153612-8.png||height="529" width="729"]] 199 199 200 200 201 - 202 202 === 2.2.5 Use UDP protocol to uplink data(Default protocol) === 203 203 204 - 205 205 This feature is supported since firmware version v1.0.1 206 206 207 -* (% style="color:blue" %)**AT+PRO=2 **(%%)~/~/208 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601 **(%%)~/~/209 -* (% 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 210 210 181 +(% style="text-align:center" %) 211 211 [[image:image-20220907153643-9.png||height="401" width="734"]] 212 212 213 - 184 +(% style="text-align:center" %) 214 214 [[image:image-20220907153703-10.png||height="309" width="738"]] 215 215 216 216 217 - 218 218 === 2.2.6 Use MQTT protocol to uplink data === 219 219 220 - 221 221 This feature is supported since firmware version v110 222 222 223 -* (% style="color:blue" %)**AT+PRO=3 **(%%)~/~/224 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883 **(%%)~/~/225 -* (% style="color:blue" %)**AT+CLIENT=CLIENT **(%%)~/~/226 -* (% style="color:blue" %)**AT+UNAME=UNAME **(%%)~/~/227 -* (% style="color:blue" %)**AT+PWD=PWD **(%%)~/~/228 -* (% style="color:blue" %)**AT+PUBTOPIC=NSE01_PUB **(%%)~/~/229 -* (% 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 230 230 200 +(% style="text-align:center" %) 231 231 [[image:image-20220907153739-11.png||height="491" width="764"]] 232 232 233 - 203 +(% style="text-align:center" %) 234 234 [[image:image-20220907153751-12.png||height="555" width="769"]] 235 235 236 - 237 237 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. 238 238 239 - 240 - 241 - 242 242 === 2.2.7 Use TCP protocol to uplink data === 243 243 244 - 245 245 This feature is supported since firmware version v110 246 246 247 -* (% style="color:blue" %)**AT+PRO=4 **(%%)~/~/ Set to use TCP protocol to uplink248 -* (% 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 249 249 215 +(% style="text-align:center" %) 250 250 [[image:image-20220907153818-13.png||height="486" width="668"]] 251 251 252 - 218 +(% style="text-align:center" %) 253 253 [[image:image-20220907153827-14.png||height="236" width="684"]] 254 254 255 - 256 - 257 257 === 2.2.8 Change Update Interval === 258 258 259 - 260 260 Users can use the below command to change the **uplink interval**. 261 261 262 -* (% style="color:blue" %)**AT+TDC=7200 **(%%)~/~/ Set Update Interval to 7200s (2 hour)225 +* **AT+TDC=7200 ** ~/~/ Set Update Interval to 7200s (2 hour) 263 263 264 - (% 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).**227 +**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).** 265 265 266 266 267 - 268 268 == 2.3 Uplink Payload == 269 269 270 - 271 271 In this mode, uplink payload includes 87 bytes in total by default. 272 272 273 273 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. 274 274 275 -(% border="2" style="background-color:#ffffcc; color:green; width:1160px" %) 276 -|(% style="width:96px" %)**Size(bytes)**|(% style="width:83px" %)**8**|(% style="width:44px" %)**2**|(% style="width:42px" %)**2**|(% style="width:124px" %)1|(% style="width:57px" %)1|(% style="width:80px" %)1|(% style="width:69px" %)2|(% style="width:134px" %)2|(% style="width:98px" %)4|(% style="width:134px" %)2|(% style="width:68px" %)2|(% style="width:125px" %)4 277 -|(% 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 ..... 236 +|**Size(bytes)**|**8**|**2**|**2**|1|1|1|2|2|4|2|2|4 237 +|**Value**|Device ID|Ver|BAT|Signal Strength|MOD|Interrupt|Soil PH|Soil Temperature|Time stamp|Soil Temperature|Soil PH|Time stamp ..... 278 278 279 279 If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NSPH01 uplink data. 280 280 241 +(% style="text-align:center" %) 281 281 [[image:image-20220907153902-15.png||height="581" width="804"]] 282 282 283 283 284 -((( 285 285 The payload is ASCII string, representative same HEX: 286 -))) 287 287 288 -((( 289 - 290 -))) 247 +0x(% style="color:red" %)f868411056754138(% style="color:blue" %)0064(% style="color:green" %)0c78(% style="color:red" %)17(% style="color:blue" %)01(% style="color:green" %)00(% style="color:red" %)**//0225010b6315537b//**010b0226631550fb//**010e022663154d77**//01110225631549f1//**011502246315466b**//01190223631542e5//**011d022163153f62**//011e022163153bde//**011e022163153859**//(%%) where: 291 291 292 -((( 293 -**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__//(%%)** 294 -))) 249 +* (% style="color:red" %)Device ID: 0xf868411056754138 = f868411056754138 250 +* (% style="color:blue" %)Version: 0x0064=100=1.0.0 251 +* (% style="color:green" %)BAT: 0x0c78 = 3192 mV = 3.192V 252 +* (% style="color:red" %)Singal: 0x17 = 23 253 +* (% style="color:blue" %)Mod: 0x01 = 1 254 +* (% style="color:green" %)Interrupt: 0x00= 0 255 +* Soil PH: 0x0225= 549 = 5.49 256 +* Soil Temperature:0x010B =267=26.7 °C 257 +* Time stamp : 0x6315537b =1662342011 ([[Unix Epoch Time>>url:http://www.epochconverter.com/]]) 258 +* Soil Temperature,Soil PH,Time stamp : 010b0226631550fb 259 +* (% style="color:red" %)8 sets of recorded data: Temperature,Soil PH,Time stamp : 010e022663154d77,....... 295 295 296 -((( 297 - 298 - 299 -where: 300 -))) 301 - 302 -* Device ID: 0xf868411056754138 = f868411056754138 303 -* Version: 0x0064=100=1.0.0 304 -* BAT: 0x0c78 = 3192 mV = 3.192V 305 -* Singal: 0x17 = 23 306 -* Mod: 0x01 = 1 307 -* Interrupt: 0x00= 0 308 -* Soil PH: 0x0225= 549 = 5.49 309 -* Soil Temperature: 0x010b =267=26.7 °C 310 -* Time stamp : 0x6315537b =1662342011 ([[Unix Epoch Time>>url:http://www.epochconverter.com/]]) 311 -* Soil Temperature,Soil PH,Time stamp : 010b0226631550fb 312 -* 8 sets of recorded data: Temperature,Soil PH,Time stamp : 010e022663154d77,....... 313 - 314 - 315 315 == 2.4 Payload Explanation and Sensor Interface == 316 316 317 - 318 318 === 2.4.1 Device ID === 319 319 320 - 321 321 By default, the Device ID equal to the last 15 bits of IMEI. 322 322 323 -User can use (% style="color:blue" %)**AT+DEUI**(%%)to set Device ID267 +User can use **AT+DEUI** to set Device ID 324 324 325 - 326 326 **Example:** 327 327 328 328 AT+DEUI=868411056754138 ... ... @@ -329,20 +329,14 @@ 329 329 330 330 The Device ID is stored in a none-erase area, Upgrade the firmware or run AT+FDR won't erase Device ID. 331 331 332 - 333 - 334 334 === 2.4.2 Version Info === 335 335 336 - 337 337 Specify the software version: 0x64=100, means firmware version 1.00. 338 338 339 339 For example: 0x00 64 : this device is NSPH01 with firmware version 1.0.0. 340 340 341 - 342 - 343 343 === 2.4.3 Battery Info === 344 344 345 - 346 346 Check the battery voltage for NSPH01. 347 347 348 348 Ex1: 0x0B45 = 2885mV ... ... @@ -349,11 +349,8 @@ 349 349 350 350 Ex2: 0x0B49 = 2889mV 351 351 352 - 353 - 354 354 === 2.4.4 Signal Strength === 355 355 356 - 357 357 NB-IoT Network signal Strength. 358 358 359 359 **Ex1: 0x1d = 29** ... ... @@ -368,25 +368,18 @@ 368 368 369 369 **99** Not known or not detectable 370 370 371 - 372 - 373 373 === 2.4.5 Soil PH === 374 374 375 - 376 376 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. 377 377 378 -For example, if the data you get from the register is (% style="color:blue" %)**__0x05 0xDC__**(%%), the PH content in the soil is309 +For example, if the data you get from the register is **__0x05 0xDC__**, the PH content in the soil is 379 379 380 - (% style="color:blue" %)**0229(H) = 549(D) /100 = 5.49.**311 +**0229(H) = 549(D) /100 = 5.49.** 381 381 382 - 383 - 384 384 === 2.4.6 Soil Temperature === 385 385 315 +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 386 386 387 -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 388 - 389 - 390 390 **Example**: 391 391 392 392 If payload is 0105H: ((0x0105 & 0x8000)>>15 === 0),temp = 0105(H)/10 = 26.1 °C ... ... @@ -393,62 +393,56 @@ 393 393 394 394 If payload is FF7EH: ((FF7E & 0x8000)>>15 ===1),temp = (FF7E(H)-FFFF(H))/10 = -12.9 °C 395 395 396 - 397 - 398 398 === 2.4.7 Timestamp === 399 399 400 - 401 401 Time stamp : 0x6315537b =1662342011 402 402 403 403 Convert Unix timestamp to time 2022-9-5 9:40:11. 404 404 405 - 406 - 407 407 === 2.4.8 Digital Interrupt === 408 408 331 +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. 409 409 410 -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. 411 - 412 412 The command is: 413 413 414 - (% 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]])**.**335 +**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]])**.** 415 415 416 416 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. 417 417 339 +Example: 418 418 419 -**Example:** 420 - 421 421 0x(00): Normal uplink packet. 422 422 423 423 0x(01): Interrupt Uplink Packet. 424 424 425 - 426 - 427 427 === 2.4.9 +5V Output === 428 428 429 - 430 430 NSPH01 will enable +5V output before all sampling and disable the +5v after all sampling. 431 431 432 432 The 5V output time can be controlled by AT Command. 433 433 434 - (% style="color:blue" %)**AT+5VT=1000**351 +**AT+5VT=1000** 435 435 436 436 Means set 5V valid time to have 1000ms. So the real 5V output will actually have 1000ms + sampling time for other sensors.** ** 437 437 438 438 439 - 440 440 == 2.5 Downlink Payload == 441 441 442 - 443 443 By default, NSPH01 prints the downlink payload to console port. 444 444 360 +(% style="text-align:center" %) 445 445 [[image:image-20220907154636-17.png]] 446 446 447 447 448 -(% style="color:blue" %)**Examples:** 449 449 450 -* (% style="color:#037691" %)** Set TDC** 451 451 366 + 367 + 368 + 369 +**Examples:** 370 + 371 +* **Set TDC** 372 + 452 452 If the payload=0100003C, it means set the END Node's TDC to 0x00003C=60(S), while type code is 01. 453 453 454 454 Payload: 01 00 00 1E TDC=30S ... ... @@ -455,19 +455,16 @@ 455 455 456 456 Payload: 01 00 00 3C TDC=60S 457 457 458 -* (% style="color:#037691" %)**379 +* **Reset** 459 459 460 460 If payload = 0x04FF, it will reset the NSPH01 461 461 462 -* (% style="color:#037691" %)**383 +* **INTMOD** 463 463 464 464 Downlink Payload: 06000003, Set AT+INTMOD=3 465 465 466 - 467 - 468 468 == 2.6 LED Indicator == 469 469 470 - 471 471 The NSPH01 has an internal LED which is to show the status of different state. 472 472 473 473 * 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) ... ... @@ -475,23 +475,16 @@ 475 475 * After NSPH01 join NB-IoT network. The LED will be ON for 3 seconds. 476 476 * For each uplink probe, LED will be on for 500ms. 477 477 396 +== 2.7 Installation and Maintain == 478 478 479 -== 2.7 Installationand Maintain==398 +=== 2.7.1 Before measurement === 480 480 481 - 482 -=== 2.7.1 Before measurement === 483 - 484 - 485 485 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. 486 486 402 +=== 2.7.2 Measurement === 487 487 404 +**Measurement the soil surface:** 488 488 489 -=== 2.7.2 Measurement === 490 - 491 - 492 -(% style="color:#037691" %)**Measurement the soil surface:** 493 - 494 - 495 495 [[image:image-20220907154700-18.png]] 496 496 497 497 Choose the proper measuring position. Split the surface soil according to the measured deep. ... ... @@ -502,18 +502,14 @@ 502 502 503 503 Put soil over the probe after insert. And start to measure. 504 504 416 +**Measurement inside soil:** 505 505 506 -(% style="color:#037691" %)**Measurement inside soil:** 507 - 508 508 Dig a hole with diameter > 20CM. 509 509 510 510 Insert the probe inside, method like measure the surface. 511 511 422 +=== 2.7.3 Maintain Probe === 512 512 513 - 514 -=== 2.7.3 Maintain Probe === 515 - 516 - 517 517 1. pH probe electrode is fragile and no strong. User must avoid strong force or hitting it. 518 518 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. 519 519 1. Probe reference electrode is also no strong, need to avoid strong force or hitting. ... ... @@ -521,14 +521,12 @@ 521 521 1. Avoid the probes to touch oily matter. Which will cause issue in accuracy. 522 522 1. The probe is IP68 can be put in water. 523 523 431 +== 2.8 PH and Temperature alarm function == 524 524 525 - ==2.8 PH andTemperaturealarmfunction ==433 +➢ AT Command: 526 526 435 +AT+ PHALARM=min,max 527 527 528 -(% style="color:#037691" %)**➢ AT Command:** 529 - 530 -(% style="color:blue" %)**AT+ PHALARM=min,max** 531 - 532 532 ² When min=3, and max≠0, Alarm higher than max 533 533 534 534 ² When min≠0, and max=0, Alarm lower than min ... ... @@ -535,11 +535,10 @@ 535 535 536 536 ² When min≠0 and max≠0, Alarm higher than max or lower than min 537 537 443 +Example: 538 538 539 - (%style="color:blue"%)**Example:**445 +AT+ PHALARM =5,8 ~/~/ Alarm when PH lower than 5. 540 540 541 -AT+ PHALARM =5,8 ~/~/ Alarm when PH lower than 5. 542 - 543 543 AT+ TEMPALARM=min,max 544 544 545 545 ² When min=0, and max≠0, Alarm higher than max ... ... @@ -548,66 +548,50 @@ 548 548 549 549 ² When min≠0 and max≠0, Alarm higher than max or lower than min 550 550 455 +Example: 551 551 552 - (%style="color:blue"%)**Example:**457 +AT+ TEMPALARM=20,30 ~/~/ Alarm when temperature lower than 20. 553 553 554 -AT+ TEMPALARM=20,30 ~/~/ Alarm when temperature lower than 20. 555 555 460 +== 2.9 Set the number of data to be uploaded and the recording time == 556 556 462 +➢ AT Command: 557 557 558 -= = 2.9Setthe numberofdatatobeuploadedandhe recording time==464 +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) 559 559 466 +AT+NOUD=8 ~/~/The device uploads 8 sets of recorded data by default. Up to 32 sets of record data can be uploaded. 560 560 561 -(% style="color:#037691" %)**➢ AT Command:** 562 562 563 -* (% 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) 564 -* (% 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. 469 +== 2.10 Read or Clear cached data == 565 565 566 - T hediagram below explains the relationship between TR, NOUD, andTDC more clearly**:**471 +➢ AT Command: 567 567 568 - [[image:image-20221009000513-1.png||height="732"width="1018"]]473 +AT+CDP ~/~/ Read cached data 569 569 570 - 571 - 572 -== 2.10 Read or Clear cached data == 573 - 574 - 575 -(% style="color:#037691" %)**➢ AT Command:** 576 - 577 -* (% style="color:blue" %)**AT+CDP** (%%) ~/~/ Read cached data 578 -* (% style="color:blue" %)**AT+CDP=0** (%%) ~/~/ Clear cached data 579 - 580 580 [[image:image-20220907154700-19.png]] 581 581 582 582 478 +AT+CDP=0 ~/~/ Clear cached data 583 583 584 -== 2.11 Calibration == 585 585 481 +== 2.11 Calibration == 586 586 587 587 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). 588 588 589 589 After stable, user can use below command to calibrate. 590 590 591 - 592 592 [[image:image-20220907154700-20.png]] 593 593 594 - 595 - 596 596 == 2.12 Firmware Change Log == 597 597 491 +Download URL & Firmware Change log: [[https:~~/~~/www.dropbox.com/sh/1zmcakvbkf24f8x/AACmq2dZ3iRB9F1nVWeEB9Moa?dl=0>>url:https://www.dropbox.com/sh/1zmcakvbkf24f8x/AACmq2dZ3iRB9F1nVWeEB9Moa?dl=0]] 598 598 599 - DownloadURL &FirmwareChange log: [[https:~~/~~/www.dropbox.com/sh/1tv07fro2pvjqj8/AAD-2wbfGfluTZfh38fQqdA_a?dl=0>>https://www.dropbox.com/sh/1tv07fro2pvjqj8/AAD-2wbfGfluTZfh38fQqdA_a?dl=0]]493 +Upgrade Instruction: [[Upgrade Firmware>>path:#H5.1200BHowtoUpgradeFirmware]] 600 600 601 -Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]] 602 - 603 - 604 - 605 605 == 2.13 Battery Analysis == 606 606 607 - 608 608 === 2.13.1 Battery Type === 609 609 610 - 611 611 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. 612 612 613 613 The battery is designed to last for several years depends on the actually use environment and update interval. ... ... @@ -620,18 +620,15 @@ 620 620 621 621 [[image:image-20220907154700-21.png]] 622 622 623 - 624 - 625 625 === 2.13.2 Power consumption Analyze === 626 626 627 - 628 628 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. 629 629 630 630 Instruction to use as below: 631 631 632 - (% 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/]]517 +**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/]] 633 633 634 - (% style="color:blue" %)**Step 2: **(%%)Open it and choose519 +**Step 2: ** Open it and choose 635 635 636 636 * Product Model 637 637 * Uplink Interval ... ... @@ -639,45 +639,34 @@ 639 639 640 640 And the Life expectation in difference case will be shown on the right. 641 641 642 - 527 +(% style="text-align:center" %) 643 643 [[image:image-20220907154700-22.jpeg]] 644 644 645 645 646 646 647 - 648 648 === 2.13.3 Battery Note === 649 649 650 - 651 651 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. 652 652 653 - 654 - 655 655 === 2.13.4 Replace the battery === 656 656 657 - 658 658 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). 659 659 660 - 661 - 662 662 = 3. Access NB-IoT Module = 663 663 664 - 665 665 Users can directly access the AT command set of the NB-IoT module. 666 666 667 667 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/]] 668 668 669 - 546 +(% style="text-align:center" %) 670 670 [[image:image-20220907154700-23.png]] 671 671 672 672 673 673 674 - 675 675 = 4. Using the AT Commands = 676 676 677 - 678 678 == 4.1 Access AT Commands == 679 679 680 - 681 681 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]] 682 682 683 683 AT+<CMD>? : Help on <CMD> ... ... @@ -688,9 +688,8 @@ 688 688 689 689 AT+<CMD>=? : Get the value 690 690 565 +**General Commands** 691 691 692 -(% style="color:#037691" %)**General Commands** 693 - 694 694 AT : Attention 695 695 696 696 AT? : Short Help ... ... @@ -734,18 +734,16 @@ 734 734 AT+ PHCAL : calibrate PH value 735 735 736 736 737 - (% style="color:#037691" %)**COAP Management**610 +**COAP Management** 738 738 739 739 AT+URI : Resource parameters 740 740 614 +**UDP Management** 741 741 742 -(% style="color:#037691" %)**UDP Management** 743 - 744 744 AT+CFM : Upload confirmation mode (only valid for UDP) 745 745 618 +**MQTT Management** 746 746 747 -(% style="color:#037691" %)**MQTT Management** 748 - 749 749 AT+CLIENT : Get or Set MQTT client 750 750 751 751 AT+UNAME : Get or Set MQTT Username ... ... @@ -756,63 +756,42 @@ 756 756 757 757 AT+SUBTOPIC : Get or Set MQTT subscription topic 758 758 630 +**Information** 759 759 760 -(% style="color:#037691" %)**Information** 761 - 762 762 AT+FDR : Factory Data Reset 763 763 764 764 AT+PWORD : Serial Access Password 765 765 766 - 767 - 768 768 = 5. FAQ = 769 769 770 - 771 771 == 5.1 How to Upgrade Firmware == 772 772 773 - 774 774 User can upgrade the firmware for 1) bug fix, 2) new feature release. 775 775 776 776 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]] 777 777 778 - (% style="color:red" %)**Notice, NSPH01 andLSPH01 share the same mother board. They use the same connection and method to update.**644 +**Notice, **NSPH01 **and **NSPH01 **share the same mother board. They use the same connection and method to update.** 779 779 780 - 781 - 782 782 == 5.2 Can I calibrate NSPH01 to different soil types? == 783 783 784 - 785 785 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]]. 786 786 787 - 788 - 789 789 = 6. Trouble Shooting = 790 790 791 - 792 792 == 6.1 Connection problem when uploading firmware == 793 793 794 - 795 795 **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]] 796 796 797 - 798 - 799 799 == 6.2 AT Command input doesn't work == 800 800 658 +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. 801 801 802 -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. 803 - 804 - 805 - 806 806 = 7. Order Info = 807 807 808 - 809 809 Part Number**:** NSPH01 810 810 811 - 812 - 813 813 = 8. Packing Info = 814 814 815 - 816 816 **Package Includes**: 817 817 818 818 * NSPH01 NB-IoT pH Sensor x 1 ... ... @@ -820,15 +820,11 @@ 820 820 821 821 **Dimension and weight**: 822 822 823 -* Device Size: cm 824 -* Device Weight: g 825 -* Package Size / pcs : cm 826 -* Weight / pcs : g 673 +* Size: 195 x 125 x 55 mm 674 +* Weight: 420g 827 827 828 - 829 829 = 9. Support = 830 830 831 - 832 832 * 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. 833 833 * 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]] 834 834
- 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