Last modified by Bei Jinggeng on 2024/03/30 17:53
<
From version < 51.2 >
edited by Xiaoling
on 2022/09/12 14:57
To version < 53.1 >
edited by David Huang
on 2022/10/08 11:47
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Xiaoling
1 +XWiki.David
Content
... ... @@ -48,6 +48,7 @@
48 48  * Micro SIM card slot
49 49  * 8500mAh Battery for long term use
50 50  
51 +
51 51  == 1.3  Specification ==
52 52  
53 53  
... ... @@ -65,6 +65,7 @@
65 65  * - B20 @H-FDD: 800MHz
66 66  * - B28 @H-FDD: 700MHz
67 67  
69 +
68 68  == 1.4  Probe Specification ==
69 69  
70 70  
... ... @@ -85,13 +85,16 @@
85 85  * IP68 Protection
86 86  * Length: 3.5 meters
87 87  
88 -== 1.5 ​Applications ==
89 89  
91 +== 1.5  ​Applications ==
92 +
93 +
90 90  * Smart Agriculture
91 91  
92 -== 1.6 Pin mapping and power on ==
93 93  
97 +== 1.6  Pin mapping and power on ==
94 94  
99 +
95 95  [[image:image-20220907153300-2.png]]
96 96  
97 97  
... ... @@ -123,9 +123,10 @@
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.
127 127  
132 +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  
134 +
129 129  [[image:image-20220907153445-4.png]]
130 130  
131 131  
... ... @@ -135,6 +135,7 @@
135 135  
136 136  User need to take out the NB-IoT module and insert the SIM card like below. ((% style="color:red" %) Pay attention to the direction(%%))
137 137  
144 +
138 138  [[image:image-20220907153505-5.png]]
139 139  
140 140  
... ... @@ -161,8 +161,8 @@
161 161  * Stop bits:  (% style="color:green" %)**1**
162 162  * Parity:  (% style="color:green" %)**None**
163 163  * Flow Control: (% style="color:green" %)**None**
164 -*
165 165  
172 +
166 166  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.
167 167  
168 168  
... ... @@ -202,11 +202,12 @@
202 202  
203 203  
204 204  This feature is supported since firmware version v1.0.1
205 -(%%)
206 -* **(% style="color:blue" %)AT+PRO=2   ** ~/~/  Set to use UDP protocol to uplink
207 -* **(% style="color:blue" %)AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/  to set UDP server address and port
208 -* **(% style="color:blue" %)AT+CFM=1       ** (%%) ~/~/  If the server does not respond, this command is unnecessar
209 209  
213 +* (% style="color:blue" %)**AT+PRO=2   ** (%%) ~/~/  Set to use UDP protocol to uplink
214 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/  to set UDP server address and port
215 +* (% style="color:blue" %)**AT+CFM=1       ** (%%) ~/~/  If the server does not respond, this command is unnecessar
216 +
217 +
210 210  [[image:image-20220907153643-9.png||height="401" width="734"]]
211 211  
212 212  
... ... @@ -213,87 +213,118 @@
213 213  [[image:image-20220907153703-10.png||height="309" width="738"]]
214 214  
215 215  
224 +
216 216  === 2.2.6 Use MQTT protocol to uplink data ===
217 217  
227 +
218 218  This feature is supported since firmware version v110
219 219  
220 -* **AT+PRO=3   ** ~/~/Set to use MQTT protocol to uplink
221 -* **AT+SERVADDR=120.24.4.116,1883   ** ~/~/Set MQTT server address and port
222 -* **AT+CLIENT=CLIENT       ** ~/~/Set up the CLIENT of MQTT
223 -* **AT+UNAME=UNAME                               **~/~/Set the username of MQTT
224 -* **AT+PWD=PWD                                        **~/~/Set the password of MQTT
225 -* **AT+PUBTOPIC=NSE01_PUB                    **~/~/Set the sending topic of MQTT
226 -* **AT+SUBTOPIC=NSE01_SUB          ** ~/~/Set the subscription topic of MQTT
230 +* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/ Set to use MQTT protocol to uplink
231 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/ Set MQTT server address and port
232 +* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%) ~/~/ Set up the CLIENT of MQTT
233 +* (% style="color:blue" %)**AT+UNAME=UNAME                               **(%%)~/~/ Set the username of MQTT
234 +* (% style="color:blue" %)**AT+PWD=PWD                                        **(%%)~/~/ Set the password of MQTT
235 +* (% style="color:blue" %)**AT+PUBTOPIC=NSE01_PUB                    **(%%)~/~/ Set the sending topic of MQTT
236 +* (% style="color:blue" %)**AT+SUBTOPIC=NSE01_SUB          ** (%%) ~/~/ Set the subscription topic of MQTT
227 227  
228 -(% style="text-align:center" %)
238 +
229 229  [[image:image-20220907153739-11.png||height="491" width="764"]]
230 230  
231 -(% style="text-align:center" %)
241 +
232 232  [[image:image-20220907153751-12.png||height="555" width="769"]]
233 233  
244 +
234 234  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.
235 235  
247 +
248 +
249 +
236 236  === 2.2.7 Use TCP protocol to uplink data ===
237 237  
252 +
238 238  This feature is supported since firmware version v110
239 239  
240 -* **AT+PRO=4   ** ~/~/ Set to use TCP protocol to uplink
241 -* **AT+SERVADDR=120.24.4.116,5600   ** ~/~/ to set TCP server address and port
255 +* (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/ Set to use TCP protocol to uplink
256 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600   ** (%%) ~/~/ to set TCP server address and port
242 242  
243 -(% style="text-align:center" %)
258 +
244 244  [[image:image-20220907153818-13.png||height="486" width="668"]]
245 245  
246 -(% style="text-align:center" %)
261 +
247 247  [[image:image-20220907153827-14.png||height="236" width="684"]]
248 248  
264 +
265 +
249 249  === 2.2.8 Change Update Interval ===
250 250  
268 +
251 251  Users can use the below command to change the **uplink interval**.
252 252  
253 -* **AT+TDC=7200      ** ~/~/ Set Update Interval to 7200s (2 hour)
271 +* (% style="color:blue" %)**AT+TDC=7200      ** (%%) ~/~/ Set Update Interval to 7200s (2 hour)
254 254  
255 -**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).**
273 +(% 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  
257 257  
276 +
258 258  == 2.3  Uplink Payload ==
259 259  
279 +
260 260  In this mode, uplink payload includes 87 bytes in total by default.
261 261  
262 262  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.
263 263  
264 -|**Size(bytes)**|**8**|**2**|**2**|1|1|1|2|2|4|2|2|4
265 -|**Value**|Device ID|Ver|BAT|Signal Strength|MOD|Interrupt|Soil PH|Soil Temperature|Time stamp|Soil Temperature|Soil PH|Time stamp  .....
284 +(% border="2" style="background-color:#ffffcc; color:green; width:1160px" %)
285 +|(% 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
286 +|(% 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  .....
266 266  
267 267  If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NSPH01 uplink data.
268 268  
269 -(% style="text-align:center" %)
270 270  [[image:image-20220907153902-15.png||height="581" width="804"]]
271 271  
272 272  
293 +(((
273 273  The payload is ASCII string, representative same HEX:
295 +)))
274 274  
275 -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:
297 +(((
298 +
299 +)))
276 276  
277 -* (% style="color:red" %)Device ID: 0xf868411056754138 = f868411056754138
278 -* (% style="color:blue" %)Version: 0x0064=100=1.0.0
279 -* (% style="color:green" %)BAT: 0x0c78 = 3192 mV = 3.192V
280 -* (% style="color:red" %)Singal: 0x17 = 23
281 -* (% style="color:blue" %)Mod: 0x01 = 1
282 -* (% style="color:green" %)Interrupt: 0x00= 0
283 -* Soil PH: 0x0225= 549 = 5.49
284 -* Soil Temperature:0x010B =267=26.7 °C
285 -* Time stamp : 0x6315537b =1662342011  ([[Unix Epoch Time>>url:http://www.epochconverter.com/]])
286 -* Soil Temperature,Soil PH,Time stamp : 010b0226631550fb
287 -* (% style="color:red" %)8 sets of recorded data: Temperature,Soil PH,Time stamp : 010e022663154d77,.......
301 +(((
302 +**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__//(%%)**
303 +)))
288 288  
305 +(((
306 +
307 +
308 +where:
309 +)))
310 +
311 +* Device ID: 0xf868411056754138 = f868411056754138
312 +* Version:  0x0064=100=1.0.0
313 +* BAT:  0x0c78 = 3192 mV = 3.192V
314 +* Singal: 0x17 = 23
315 +* Mod:  0x01 = 1
316 +* Interrupt: 0x00= 0
317 +* Soil PH:  0x0225= 549 = 5.49
318 +* Soil Temperature: 0x010b =267=26.7 °C
319 +* Time stamp :  0x6315537b =1662342011  ([[Unix Epoch Time>>url:http://www.epochconverter.com/]])
320 +* Soil Temperature,Soil PH,Time stamp :  010b0226631550fb
321 +* 8 sets of recorded data: Temperature,Soil PH,Time stamp :  010e022663154d77,.......
322 +
323 +
324 +
289 289  == 2.4  Payload Explanation and Sensor Interface ==
290 290  
327 +
291 291  === 2.4.1  Device ID ===
292 292  
330 +
293 293  By default, the Device ID equal to the last 15 bits of IMEI.
294 294  
295 -User can use **AT+DEUI** to set Device ID
333 +User can use (% style="color:blue" %)**AT+DEUI** (%%)to set Device ID
296 296  
335 +
297 297  **Example:**
298 298  
299 299  AT+DEUI=868411056754138
... ... @@ -300,14 +300,20 @@
300 300  
301 301  The Device ID is stored in a none-erase area, Upgrade the firmware or run AT+FDR won't erase Device ID.
302 302  
342 +
343 +
303 303  === 2.4.2  Version Info ===
304 304  
346 +
305 305  Specify the software version: 0x64=100, means firmware version 1.00.
306 306  
307 307  For example: 0x00 64 : this device is NSPH01 with firmware version 1.0.0.
308 308  
351 +
352 +
309 309  === 2.4.3  Battery Info ===
310 310  
355 +
311 311  Check the battery voltage for NSPH01.
312 312  
313 313  Ex1: 0x0B45 = 2885mV
... ... @@ -314,8 +314,11 @@
314 314  
315 315  Ex2: 0x0B49 = 2889mV
316 316  
362 +
363 +
317 317  === 2.4.4  Signal Strength ===
318 318  
366 +
319 319  NB-IoT Network signal Strength.
320 320  
321 321  **Ex1: 0x1d = 29**
... ... @@ -330,18 +330,25 @@
330 330  
331 331  **99**    Not known or not detectable
332 332  
381 +
382 +
333 333  === 2.4.5  Soil PH ===
334 334  
385 +
335 335  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.
336 336  
337 -For example, if the data you get from the register is **__0x05 0xDC__**, the PH content in the soil is
388 +For example, if the data you get from the register is (% style="color:blue" %)**__0x05 0xDC__**(%%), the PH content in the soil is
338 338  
339 -**0229(H) = 549(D) /100 = 5.49.**
390 +(% style="color:blue" %)**0229(H) = 549(D) /100 = 5.49.**
340 340  
392 +
393 +
341 341  === 2.4.6  Soil Temperature ===
342 342  
343 -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
344 344  
397 +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
398 +
399 +
345 345  **Example**:
346 346  
347 347  If payload is 0105H: ((0x0105 & 0x8000)>>15 === 0),temp = 0105(H)/10 = 26.1 °C
... ... @@ -348,56 +348,62 @@
348 348  
349 349  If payload is FF7EH: ((FF7E & 0x8000)>>15 ===1),temp = (FF7E(H)-FFFF(H))/10 = -12.9 °C
350 350  
406 +
407 +
351 351  === 2.4.7  Timestamp ===
352 352  
410 +
353 353  Time stamp : 0x6315537b =1662342011
354 354  
355 355  Convert Unix timestamp to time 2022-9-5 9:40:11.
356 356  
415 +
416 +
357 357  === 2.4.8  Digital Interrupt ===
358 358  
359 -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.
360 360  
420 +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.
421 +
361 361  The command is:
362 362  
363 -**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]])**.**
424 +(% 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]])**.**
364 364  
365 365  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.
366 366  
367 -Example:
368 368  
429 +**Example:**
430 +
369 369  0x(00): Normal uplink packet.
370 370  
371 371  0x(01): Interrupt Uplink Packet.
372 372  
435 +
436 +
373 373  === 2.4.9  ​+5V Output ===
374 374  
439 +
375 375  NSPH01 will enable +5V output before all sampling and disable the +5v after all sampling. 
376 376  
377 377  The 5V output time can be controlled by AT Command.
378 378  
379 -**AT+5VT=1000**
444 +(% style="color:blue" %)**AT+5VT=1000**
380 380  
381 381  Means set 5V valid time to have 1000ms. So the real 5V output will actually have 1000ms + sampling time for other sensors.** **
382 382  
383 383  
449 +
384 384  == 2.5  Downlink Payload ==
385 385  
452 +
386 386  By default, NSPH01 prints the downlink payload to console port.
387 387  
388 -(% style="text-align:center" %)
389 389  [[image:image-20220907154636-17.png]]
390 390  
391 391  
458 +(% style="color:blue" %)**Examples:**
392 392  
460 +* (% style="color:#037691" %)** Set TDC**
393 393  
394 -
395 -
396 -
397 -**Examples:**
398 -
399 -* **Set TDC**
400 -
401 401  If the payload=0100003C, it means set the END Node's TDC to 0x00003C=60(S), while type code is 01.
402 402  
403 403  Payload:    01 00 00 1E    TDC=30S
... ... @@ -404,16 +404,19 @@
404 404  
405 405  Payload:    01 00 00 3C    TDC=60S
406 406  
407 -* **Reset**
468 +* (% style="color:#037691" %)** Reset**
408 408  
409 409  If payload = 0x04FF, it will reset the NSPH01
410 410  
411 -* **INTMOD**
472 +* (% style="color:#037691" %)** INTMOD**
412 412  
413 413  Downlink Payload: 06000003, Set AT+INTMOD=3
414 414  
476 +
477 +
415 415  == 2.6  ​LED Indicator ==
416 416  
480 +
417 417  The NSPH01 has an internal LED which is to show the status of different state.
418 418  
419 419  * 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)
... ... @@ -421,16 +421,24 @@
421 421  * After NSPH01 join NB-IoT network. The LED will be ON for 3 seconds.
422 422  * For each uplink probe, LED will be on for 500ms.
423 423  
424 -== 2.7 Installation and Maintain ==
425 425  
426 -=== 2.7.1 Before measurement ===
427 427  
490 +== 2.7  Installation and Maintain ==
491 +
492 +
493 +=== 2.7.1  Before measurement ===
494 +
495 +
428 428  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. 
429 429  
430 -=== 2.7.2 Measurement ===
431 431  
432 -**Measurement the soil surface:**
433 433  
500 +=== 2.7.2  Measurement ===
501 +
502 +
503 +(% style="color:#037691" %)**Measurement the soil surface:**
504 +
505 +
434 434  [[image:image-20220907154700-18.png]] ​
435 435  
436 436  Choose the proper measuring position. Split the surface soil according to the measured deep.
... ... @@ -441,14 +441,18 @@
441 441  
442 442  Put soil over the probe after insert. And start to measure.
443 443  
444 -**Measurement inside soil:**
445 445  
517 +(% style="color:#037691" %)**Measurement inside soil:**
518 +
446 446  Dig a hole with diameter > 20CM.
447 447  
448 448  Insert the probe inside, method like measure the surface.
449 449  
450 -=== 2.7.3 Maintain Probe ===
451 451  
524 +
525 +=== 2.7.3  Maintain Probe ===
526 +
527 +
452 452  1. pH probe electrode is fragile and no strong. User must avoid strong force or hitting it.
453 453  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.
454 454  1. Probe reference electrode is also no strong, need to avoid strong force or hitting.
... ... @@ -456,12 +456,15 @@
456 456  1. Avoid the probes to touch oily matter. Which will cause issue in accuracy.
457 457  1. The probe is IP68 can be put in water.
458 458  
459 -== 2.8 PH and Temperature alarm function ==
460 460  
461 -➢ AT Command:
462 462  
463 -AT+ PHALARM=min,max
537 +== 2.8  PH and Temperature alarm function ==
464 464  
539 +
540 +(% style="color:#037691" %)**➢ AT Command:**
541 +
542 +(% style="color:blue" %)**AT+ PHALARM=min,max**
543 +
465 465  ² When min=3, and max≠0, Alarm higher than max
466 466  
467 467  ² When min≠0, and max=0, Alarm lower than min
... ... @@ -468,10 +468,11 @@
468 468  
469 469  ² When min≠0 and max≠0, Alarm higher than max or lower than min
470 470  
471 -Example:
472 472  
473 -AT+ PHALARM =5,8 ~/~/ Alarm when PH lower than 5.
551 +(% style="color:blue" %)**Example:**
474 474  
553 +AT+ PHALARM =5,8  ~/~/ Alarm when PH lower than 5.
554 +
475 475  AT+ TEMPALARM=min,max
476 476  
477 477  ² When min=0, and max≠0, Alarm higher than max
... ... @@ -480,50 +480,64 @@
480 480  
481 481  ² When min≠0 and max≠0, Alarm higher than max or lower than min
482 482  
483 -Example:
484 484  
485 -AT+ TEMPALARM=20,30 ~/~/ Alarm when temperature lower than 20.
564 +(% style="color:blue" %)**Example:**
486 486  
566 +AT+ TEMPALARM=20,30  ~/~/ Alarm when temperature lower than 20.
487 487  
488 -== 2.9 Set the number of data to be uploaded and the recording time ==
489 489  
490 -➢ AT Command:
491 491  
492 -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)
570 +== 2.9  Set the number of data to be uploaded and the recording time ==
493 493  
494 -AT+NOUD=8  ~/~/The device uploads 8 sets of recorded data by default. Up to 32 sets of record data can be uploaded.
495 495  
573 +(% style="color:#037691" %)**➢ AT Command:**
496 496  
497 -== 2.10 Read or Clear cached data ==
575 +* (% 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)
576 +* (% 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.
498 498  
499 -➢ AT Command:
500 500  
501 -AT+CDP ~/~/ Read cached data
579 +This link explains the relationship between TR, NOUD and TDC more clearly** : **[[https:~~/~~/www.processon.com/view/link/6340e606e401fd390891af87>>url:https://www.processon.com/view/link/6340e606e401fd390891af87]]
502 502  
581 +== 2.10  Read or Clear cached data ==
582 +
583 +
584 +(% style="color:#037691" %)**➢ AT Command:**
585 +
586 +* (% style="color:blue" %)**AT+CDP**        (%%) ~/~/  Read cached data
587 +* (% style="color:blue" %)**AT+CDP=0**    (%%) ~/~/  Clear cached data
588 +
589 +
503 503  [[image:image-20220907154700-19.png]]
504 504  
505 505  
506 -AT+CDP=0 ~/~/ Clear cached data
507 507  
594 +== 2.11  Calibration ==
508 508  
509 -== 2.11 Calibration ==
510 510  
511 511  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).
512 512  
513 513  After stable, user can use below command to calibrate.
514 514  
601 +
515 515  [[image:image-20220907154700-20.png]] ​
516 516  
604 +
605 +
517 517  == 2.12  ​Firmware Change Log ==
518 518  
519 -Download URL & Firmware Change log: [[https:~~/~~/www.dropbox.com/sh/1zmcakvbkf24f8x/AACmq2dZ3iRB9F1nVWeEB9Moa?dl=0>>url:https://www.dropbox.com/sh/1zmcakvbkf24f8x/AACmq2dZ3iRB9F1nVWeEB9Moa?dl=0]]
520 520  
521 -Upgrade Instruction: [[Upgrade Firmware>>path:#H5.1200BHowtoUpgradeFirmware]]
609 +Download URL & Firmware Change log: [[https:~~/~~/www.dropbox.com/sh/1tv07fro2pvjqj8/AAD-2wbfGfluTZfh38fQqdA_a?dl=0>>https://www.dropbox.com/sh/1tv07fro2pvjqj8/AAD-2wbfGfluTZfh38fQqdA_a?dl=0]]
522 522  
611 +Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
612 +
613 +
614 +
523 523  == 2.13  ​Battery Analysis ==
524 524  
617 +
525 525  === 2.13.1  ​Battery Type ===
526 526  
620 +
527 527  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.
528 528  
529 529  The battery is designed to last for several years depends on the actually use environment and update interval. 
... ... @@ -536,15 +536,18 @@
536 536  
537 537  [[image:image-20220907154700-21.png]] ​
538 538  
633 +
634 +
539 539  === 2.13.2  Power consumption Analyze ===
540 540  
637 +
541 541  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.
542 542  
543 543  Instruction to use as below:
544 544  
545 -**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/]]
642 +(% 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/]]
546 546  
547 -**Step 2: ** Open it and choose
644 +(% style="color:blue" %)**Step 2: **(%%) Open it and choose
548 548  
549 549  * Product Model
550 550  * Uplink Interval
... ... @@ -552,34 +552,45 @@
552 552  
553 553  And the Life expectation in difference case will be shown on the right.
554 554  
555 -(% style="text-align:center" %)
652 +
556 556  [[image:image-20220907154700-22.jpeg]]
557 557  
558 558  ​
559 559  
657 +
560 560  === 2.13.3  ​Battery Note ===
561 561  
660 +
562 562  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.
563 563  
663 +
664 +
564 564  === 2.13.4  Replace the battery ===
565 565  
667 +
566 566  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).
567 567  
670 +
671 +
568 568  = 3. ​ Access NB-IoT Module =
569 569  
674 +
570 570  Users can directly access the AT command set of the NB-IoT module.
571 571  
572 572  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/]] 
573 573  
574 -(% style="text-align:center" %)
679 +
575 575  [[image:image-20220907154700-23.png]]
576 576  
577 577  ​
578 578  
684 +
579 579  = 4.  Using the AT Commands =
580 580  
687 +
581 581  == 4.1  Access AT Commands ==
582 582  
690 +
583 583  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]]
584 584  
585 585  AT+<CMD>?  : Help on <CMD>
... ... @@ -590,8 +590,9 @@
590 590  
591 591  AT+<CMD>=?  : Get the value
592 592  
593 -**General Commands**      
594 594  
702 +(% style="color:#037691" %)**General Commands**      
703 +
595 595  AT  : Attention       
596 596  
597 597  AT?  : Short Help     
... ... @@ -635,16 +635,18 @@
635 635  AT+ PHCAL  : calibrate PH value
636 636  
637 637  
638 -**COAP Management**      
747 +(% style="color:#037691" %)**COAP Management**      
639 639  
640 640  AT+URI            : Resource parameters
641 641  
642 -**UDP Management**
643 643  
752 +(% style="color:#037691" %)**UDP Management**
753 +
644 644  AT+CFM          : Upload confirmation mode (only valid for UDP)
645 645  
646 -**MQTT Management**
647 647  
757 +(% style="color:#037691" %)**MQTT Management**
758 +
648 648  AT+CLIENT               : Get or Set MQTT client
649 649  
650 650  AT+UNAME  : Get or Set MQTT Username
... ... @@ -655,42 +655,63 @@
655 655  
656 656  AT+SUBTOPIC  : Get or Set MQTT subscription topic
657 657  
658 -**Information**          
659 659  
770 +(% style="color:#037691" %)**Information**          
771 +
660 660  AT+FDR  : Factory Data Reset
661 661  
662 662  AT+PWORD  : Serial Access Password
663 663  
776 +
777 +
664 664  = ​5.  FAQ =
665 665  
780 +
666 666  == 5.1 ​ How to Upgrade Firmware ==
667 667  
783 +
668 668  User can upgrade the firmware for 1) bug fix, 2) new feature release.
669 669  
670 670  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]]
671 671  
672 -**Notice, **NSPH01 **and **NSPH01 **share the same mother board. They use the same connection and method to update.**
788 +(% style="color:red" %)**Notice, NSPH01 and LSPH01 share the same mother board. They use the same connection and method to update.**
673 673  
790 +
791 +
674 674  == 5.2  Can I calibrate NSPH01 to different soil types? ==
675 675  
794 +
676 676  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]].
677 677  
797 +
798 +
678 678  = 6.  Trouble Shooting =
679 679  
801 +
680 680  == 6.1  ​Connection problem when uploading firmware ==
681 681  
804 +
682 682  **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]]
683 683  
807 +
808 +
684 684  == 6.2  AT Command input doesn't work ==
685 685  
686 -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.
687 687  
812 +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.
813 +
814 +
815 +
688 688  = 7. ​ Order Info =
689 689  
818 +
690 690  Part Number**:** NSPH01
691 691  
821 +
822 +
692 692  = 8.  Packing Info =
693 693  
825 +
694 694  **Package Includes**:
695 695  
696 696  * NSPH01 NB-IoT pH Sensor x 1
... ... @@ -698,11 +698,16 @@
698 698  
699 699  **Dimension and weight**:
700 700  
701 -* Size: 195 x 125 x 55 mm
702 -* Weight:   420g
833 +* Device Size: cm
834 +* Device Weight: g
835 +* Package Size / pcs : cm
836 +* Weight / pcs : g
703 703  
838 +
839 +
704 704  = 9.  Support =
705 705  
842 +
706 706  * 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.
707 707  * 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]]
708 708  
image-20220923101327-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +12.1 KB
Content

Applications

Navigation

Copyright ©2010-2024 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0