<
From version < 26.1 >
edited by David Huang
on 2022/09/07 17:38
To version < 27.1 >
edited by David Huang
on 2022/09/07 17:44
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -119,9 +119,9 @@
119 119  
120 120  [[image:image-20220907171221-5.png]]
121 121  
122 -== **2.2 ​ Configure the NLMS01** ==
122 +== 2.2 ​ Configure the NLMS01 ==
123 123  
124 -**2.2.1 Test Requirement**
124 +=== 2.2.1 Test Requirement ===
125 125  
126 126  To use NLMS01 in your city, make sure meet below requirements:
127 127  
... ... @@ -133,7 +133,7 @@
133 133  
134 134  [[image:image-20220907171221-6.png]] ​
135 135  
136 -**2.2.2 Insert SIM card**
136 +=== 2.2.2 Insert SIM card ===
137 137  
138 138  Insert the NB-IoT Card get from your provider.
139 139  
... ... @@ -141,7 +141,7 @@
141 141  
142 142  [[image:image-20220907171221-7.png]] ​
143 143  
144 -**2.2.3 Connect USB – TTL to NLMS01 to configure it**
144 +=== 2.2.3 Connect USB – TTL to NLMS01 to configure it ===
145 145  
146 146  User need to configure NLMS01 via serial port to set the **Server Address** / **Uplink Topic** to define where and how-to uplink packets. NLMS01 support AT Commands, user can use a USB to TTL adapter to connect to NLMS01 and use AT Commands to configure it, as below.
147 147  
... ... @@ -167,7 +167,7 @@
167 167  
168 168  **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]]
169 169  
170 -**2.2.4 Use CoAP protocol to uplink data**
170 +=== 2.2.4 Use CoAP protocol to uplink data ===
171 171  
172 172  **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/]]
173 173  
... ... @@ -185,7 +185,7 @@
185 185  
186 186  [[image:image-20220907171221-10.png]] ​
187 187  
188 -**2.2.5 Use UDP protocol to uplink data(Default protocol)**
188 +=== 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
189 189  
190 190  This feature is supported since firmware version v1.0.1
191 191  
... ... @@ -199,7 +199,7 @@
199 199  
200 200  ​
201 201  
202 -**2.2.6 Use MQTT protocol to uplink data**
202 +=== 2.2.6 Use MQTT protocol to uplink data ===
203 203  
204 204  This feature is supported since firmware version v110
205 205  
... ... @@ -219,7 +219,7 @@
219 219  
220 220  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.
221 221  
222 -**2.2.7 Use TCP protocol to uplink data**
222 +=== 2.2.7 Use TCP protocol to uplink data ===
223 223  
224 224  This feature is supported since firmware version v110
225 225  
... ... @@ -232,7 +232,7 @@
232 232  
233 233  ​
234 234  
235 -**2.2.8 Change Update Interval**
235 +=== 2.2.8 Change Update Interval ===
236 236  
237 237  User can use below command to change the **uplink interval**.
238 238  
... ... @@ -274,7 +274,7 @@
274 274  
275 275  == 2.4  Payload Explanation and Sensor Interface ==
276 276  
277 -**2.4.1  Device ID**
277 +=== 2.4.1  Device ID ===
278 278  
279 279  By default, the Device ID equal to the last 15 bits of IMEI.
280 280  
... ... @@ -286,13 +286,13 @@
286 286  
287 287  The Device ID is stored in a none-erase area, Upgrade the firmware or run AT+FDR won't erase Device ID.
288 288  
289 -**2.4.2  Version Info**
289 +=== 2.4.2  Version Info ===
290 290  
291 291  Specify the software version: 0x64=100, means firmware version 1.00.
292 292  
293 293  For example: 0x00 64 : this device is NLMS01 with firmware version 1.0.0.
294 294  
295 -**2.4.3  Battery Info**
295 +=== 2.4.3  Battery Info ===
296 296  
297 297  Check the battery voltage for NLMS01.
298 298  
... ... @@ -300,7 +300,7 @@
300 300  
301 301  Ex2: 0x0B49 = 2889mV
302 302  
303 -**2.4.4  Signal Strength**
303 +=== 2.4.4  Signal Strength ===
304 304  
305 305  NB-IoT Network signal Strength.
306 306  
... ... @@ -316,7 +316,7 @@
316 316  
317 317  **99**    Not known or not detectable
318 318  
319 -**2.4.5  Leaf** moisture
319 +=== 2.4.5  Leaf moisture ===
320 320  
321 321  Get the moisture of the **Leaf**. The value range of the register is 300-1000(Decimal), divide this value by 100 to get the percentage of moisture in the **Leaf**.
322 322  
... ... @@ -324,7 +324,7 @@
324 324  
325 325  **0229(H) = 549(D) /100 = 54.9.**
326 326  
327 -**2.4.6  Leaf Temperature**
327 +=== 2.4.6  Leaf Temperature ===
328 328  
329 329  Get the temperature in the **Leaf**. The value range of the register is -4000 - +800(Decimal), divide this value by 100 to get the temperature in the **Leaf**. For example, if the data you get from the register is **__0x09 0xEC__**, the temperature content in the **Leaf **is
330 330  
... ... @@ -334,13 +334,13 @@
334 334  
335 335  If payload is FF7EH: ((FF7E & 0x8000)>>15 ===1),temp = (FF7E(H)-FFFF(H))/10 = -12.9 °C
336 336  
337 -**2.4.7  Timestamp**
337 +=== 2.4.7  Timestamp ===
338 338  
339 339  Time stamp : 0x6315537b =1662342011
340 340  
341 341  Convert Unix timestamp to time 2022-9-5 9:40:11.
342 342  
343 -**2.4.8  Digital Interrupt**
343 +=== 2.4.8  Digital Interrupt ===
344 344  
345 345  Digital Interrupt refers to pin **GPIO_EXTI**, and there are different trigger methods. When there is a trigger, the NLMS01 will send a packet to the server.
346 346  
... ... @@ -356,7 +356,7 @@
356 356  
357 357  0x(01): Interrupt Uplink Packet.
358 358  
359 -**2.4.9  ​+5V Output**
359 +=== 2.4.9  ​+5V Output ===
360 360  
361 361  NLMS01 will enable +5V output before all sampling and disable the +5v after all sampling. 
362 362  
... ... @@ -463,7 +463,7 @@
463 463  
464 464  == 2.12  ​Battery Analysis ==
465 465  
466 -**2.12.1  ​Battery Type**
466 +=== 2.12.1  ​Battery Type ===
467 467  
468 468  The NLMS01 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.
469 469  
... ... @@ -477,7 +477,7 @@
477 477  
478 478  [[image:image-20220907171221-21.png]] ​
479 479  
480 -**2.12.2  Power consumption Analyze**
480 +=== 2.12.2  Power consumption Analyze ===
481 481  
482 482  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.
483 483  
... ... @@ -495,11 +495,11 @@
495 495  
496 496  [[image:image-20220907171221-22.jpeg]] ​
497 497  
498 -**2.12.3  ​Battery Note**
498 +=== 2.12.3  ​Battery Note ===
499 499  
500 500  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.
501 501  
502 -**2.12.4  Replace the battery**
502 +=== 2.12.4  Replace the battery ===
503 503  
504 504  The default battery pack of NLMS01 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).
505 505  
... ... @@ -513,7 +513,7 @@
513 513  
514 514  = 4.  Using the AT Commands =
515 515  
516 -**4.1  Access AT Commands**
516 +== 4.1  Access AT Commands ==
517 517  
518 518  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]]
519 519  
... ... @@ -591,7 +591,7 @@
591 591  
592 592  = ​5.  FAQ =
593 593  
594 -**5.1 ​ How to Upgrade Firmware**
594 +== 5.1 ​ How to Upgrade Firmware ==
595 595  
596 596  User can upgrade the firmware for 1) bug fix, 2) new feature release.
597 597  
... ... @@ -601,11 +601,11 @@
601 601  
602 602  = 6.  Trouble Shooting =
603 603  
604 -**6.1  ​Connection problem when uploading firmware**
604 +== 6.1  ​Connection problem when uploading firmware ==
605 605  
606 606  **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]]
607 607  
608 -**6.2  AT Command input doesn't work**
608 +== 6.2  AT Command input doesn't work ==
609 609  
610 610  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.
611 611  
Copyright ©2010-2022 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0