Wiki source code of NLMS01-NB-IoT Leaf Moisture Sensor User Manual

Version 33.4 by Xiaoling on 2022/09/13 09:41

version	line-number	content
28.1	1	(% style="text-align:center" %)
	2	[[image:image-20220907171221-1.jpeg]]
25.1	3
28.1	4
25.1	5
28.1	6	{{toc/}}
25.1	7
28.1	8
	9
32.2	10	= 1. Introduction =
25.1	11
	12
32.2	13	== 1.1 What is NLMS01 Leaf Moisture Sensor ==
26.1	14
25.1	15
32.2	16	The Dragino NLMS01 is a (% style="color:blue" %)NB-IOT Leaf Moisture Sensor(%%) for IoT of Agriculture. It is designed to measure the leaf moisture and temperature, so to send to the platform to analyze the leaf status such as : watering, moisturizing, dew, frozen. The probe is IP67 waterproof.
25.1	17
32.2	18	NLMS01 detects leaf's(% style="color:blue" %) moisture and temperature use FDR method(%%), it senses the dielectric constant cause by liquid over the leaf surface, and cover the value to leaf moisture. The probe is design in a leaf shape to best simulate the real leaf characterizes. The probe has as density as 15 leaf vein lines per centimeter which make it can senses small drop and more accuracy.
	19
25.1	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.
32.2	21	\\NLMS01 supports different uplink methods include (% style="color:blue" %)TCP,MQTT,UDP and CoAP (%%)for different application requirement.
	22	\\NLMS01 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 NLMS01, user needs to check if there is NB-IoT coverage in local area and with the bands NLMS01 supports. If the local operate support it, user needs to get a (% style="color:blue" %)NB-IoT SIM card(%%) from local operator and install NLMS01 to get NB-IoT network connection.
25.1	24
32.2	25
25.1	26	[[image:image-20220907171221-2.png]]
	27
32.2	28
25.1	29	[[image:image-20220907171221-3.png]]
	30
	31
	32
32.2	33	== 1.2 Features ==
25.1	34
32.2	35
	36	* NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD
	37	* Monitor Leaf moisture
	38	* Monitor Leaf temperature
	39	* Moisture and Temperature alarm function
	40	* Monitor Battery Level
	41	* Uplink on periodically
	42	* Downlink to change configure
	43	* IP66 Waterproof Enclosure
	44	* IP67 rate for the Sensor Probe
	45	* Ultra-Low Power consumption
	46	* AT Commands to change parameters
	47	* Micro SIM card slot for NB-IoT SIM
	48	* 8500mAh Battery for long term use
	49
	50	(((
	51
	52
	53
	54
26.1	55	)))
25.1	56
26.1	57	== 1.3 Specification ==
25.1	58
	59
32.2	60	(% style="color:#037691" %)Common DC Characteristics:
	61
25.1	62	* Supply Voltage: 2.1v ~~ 3.6v
	63	* Operating Temperature: -40 ~~ 85°C
	64
32.2	65	(% style="color:#037691" %)NB-IoT Spec:
	66
25.1	67	* - B1 @H-FDD: 2100MHz
	68	* - B3 @H-FDD: 1800MHz
	69	* - B8 @H-FDD: 900MHz
	70	* - B5 @H-FDD: 850MHz
	71	* - B20 @H-FDD: 800MHz
	72	* - B28 @H-FDD: 700MHz
	73
33.4	74
	75
	76
33.2	77	== 1.4 Probe Specification ==
32.2	78
	79
33.2	80	(% style="color:#037691" %)Leaf Moisture: percentage of water drop over total leaf surface
25.1	81
	82	* Range 0-100%
	83	* Resolution: 0.1%
	84	* Accuracy: ±3%（0-50%）；±6%（>50%）
	85	* IP67 Protection
	86	* Length: 3.5 meters
	87
33.4	88
	89
33.2	90	(% style="color:#037691" %)Leaf Temperature:
25.1	91
	92	* Range -50℃～80℃
	93	* Resolution: 0.1℃
	94	* Accuracy: <±0.5℃(-10℃～70℃)，<±1.0℃ (others)
	95	* IP67 Protection
	96	* Length: 3.5 meters
	97
33.4	98
	99
	100
33.2	101	== 1.5 Applications ==
25.1	102
33.2	103
25.1	104	* Smart Agriculture
	105
33.4	106
	107
	108
33.2	109	== 1.6 Pin mapping and power on ==
25.1	110
33.2	111
25.1	112	[[image:image-20220907171221-4.png]]
	113
	114	~
	115
33.2	116
26.1	117	= 2. Use NLMS01 to communicate with IoT Server =
25.1	118
33.2	119
26.1	120	== 2.1 How it works ==
25.1	121
33.2	122
25.1	123	The NLMS01 is equipped with a NB-IoT module, the pre-loaded firmware in NLMS01 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 NLMS01.
	124
	125	The diagram below shows the working flow in default firmware of NLMS01:
	126
33.2	127
25.1	128	[[image:image-20220907171221-5.png]]
	129
33.2	130
	131
27.1	132	== 2.2 Configure the NLMS01 ==
25.1	133
33.2	134
27.1	135	=== 2.2.1 Test Requirement ===
25.1	136
33.2	137
25.1	138	To use NLMS01 in your city, make sure meet below requirements:
	139
	140	* Your local operator has already distributed a NB-IoT Network there.
	141	* The local NB-IoT network used the band that NLMS01 supports.
	142	* Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
	143
33.2	144	Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8. The NLMS01 will use(% style="color:#037691" %) CoAP(120.24.4.116:5683) (%%)or raw(% style="color:#037691" %) UDP(120.24.4.116:5601) or(%%) (% style="color:#037691" %)MQTT(120.24.4.116:1883)(%%)or (% style="color:#037691" %)TCP(120.24.4.116:5600)(%%)protocol to send data to the test server
25.1	145
33.2	146
25.1	147	[[image:image-20220907171221-6.png]]
	148
33.2	149
	150
27.1	151	=== 2.2.2 Insert SIM card ===
25.1	152
33.2	153
25.1	154	Insert the NB-IoT Card get from your provider.
	155
	156	User need to take out the NB-IoT module and insert the SIM card like below:
	157
33.2	158
25.1	159	[[image:image-20220907171221-7.png]]
	160
33.2	161
	162
27.1	163	=== 2.2.3 Connect USB – TTL to NLMS01 to configure it ===
25.1	164
	165
33.2	166	User need to configure NLMS01 via serial port to set the (% style="color:#037691" %)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.
25.1	167
	168
33.2	169	(% style="color:blue" %)Connection:
25.1	170
33.2	171	~ (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND(%%)
25.1	172
33.2	173	~ (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD(%%)
	174
	175	~ (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD(%%)
	176
	177
25.1	178	In the PC, use below serial tool settings:
	179
33.2	180	* Baud: (% style="color:green" %)9600
	181	* Data bits: (% style="color:green" %)8(%%)
	182	* Stop bits: (% style="color:green" %)1
	183	* Parity: (% style="color:green" %)None
	184	* Flow Control: (% style="color:green" %)None
25.1	185
33.2	186	Make sure the switch is in FLASH position, then power on device by connecting the jumper on NLMS01. NLMS01 will output system info once power on as below, we can enter the (% style="color:green" %)password: 12345678(%%) to access AT Command input.
25.1	187
33.2	188	[[image:image-20220913090720-1.png]]
25.1	189
	190
33.2	191	(% 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]]
	192
	193
	194
27.1	195	=== 2.2.4 Use CoAP protocol to uplink data ===
25.1	196
	197
33.2	198	(% style="color:red" %)Note: if you don't have CoAP server, you can refer this link to set up one: (%%)[[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/>>url:http://wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/]]
25.1	199
	200
33.2	201	(% style="color:blue" %)Use below commands:
	202
	203	* (% style="color:#037691" %)AT+PRO=1 (%%) ~/~/ Set to use CoAP protocol to uplink
	204	* (% style="color:#037691" %)AT+SERVADDR=120.24.4.116,5683 (%%) ~/~/ to set CoAP server address and port
	205	* (% style="color:#037691" %)AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" (%%) ~/~/ Set COAP resource path
	206
25.1	207	For parameter description, please refer to AT command set
	208
	209	[[image:image-20220907171221-9.png]]
	210
	211
33.2	212	After configure the server address and (% style="color:#037691" %)reset the device(%%) (via AT+ATZ ), NLMS01 will start to uplink sensor values to CoAP server.
	213
25.1	214	[[image:image-20220907171221-10.png]]
	215
33.2	216
	217
27.1	218	=== 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
25.1	219
33.2	220
25.1	221	This feature is supported since firmware version v1.0.1
	222
33.2	223	* (% style="color:#037691" %)AT+PRO=2 (%%) ~/~/ Set to use UDP protocol to uplink
33.4	224	* (% style="color:#037691" %)AT+SERVADDR=120.24.4.116,5601 (%%) ~/~/ to set UDP server address and port
33.2	225	* (% style="color:#037691" %)AT+CFM=1 (%%) ~/~/ If the server does not respond, this command is unnecessary
25.1	226
33.2	227
	228
25.1	229	[[image:image-20220907171221-11.png]]
	230
33.2	231
25.1	232	[[image:image-20220907171221-12.png]]
	233
	234
	235
33.2	236
27.1	237	=== 2.2.6 Use MQTT protocol to uplink data ===
25.1	238
33.2	239
25.1	240	This feature is supported since firmware version v110
	241
33.2	242	* (% style="color:#037691" %)AT+PRO=3 (%%) ~/~/ Set to use MQTT protocol to uplink
	243	* (% style="color:#037691" %)AT+SERVADDR=120.24.4.116,1883 (%%) ~/~/ Set MQTT server address and port
	244	* (% style="color:#037691" %)AT+CLIENT=CLIENT (%%) ~/~/ Set up the CLIENT of MQTT
	245	* (% style="color:#037691" %)AT+UNAME=UNAME (%%) ~/~/ Set the username of MQTT
	246	* (% style="color:#037691" %)AT+PWD=PWD (%%) ~/~/ Set the password of MQTT
	247	* (% style="color:#037691" %)AT+PUBTOPIC=PUB (%%) ~/~/ Set the sending topic of MQTT
	248	* (% style="color:#037691" %)AT+SUBTOPIC=SUB (%%) ~/~/ Set the subscription topic of MQTT
25.1	249
33.2	250
	251
25.1	252	[[image:image-20220907171221-13.png]]
	253
33.2	254
	255
25.1	256	[[image:image-20220907171221-14.png]]
	257
	258
	259
	260	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.
	261
33.2	262
	263
27.1	264	=== 2.2.7 Use TCP protocol to uplink data ===
25.1	265
33.2	266
25.1	267	This feature is supported since firmware version v110
	268
33.2	269	* (% style="color:#037691" %)AT+PRO=4 (%%) ~/~/ Set to use TCP protocol to uplink
	270	* (% style="color:#037691" %)AT+SERVADDR=120.24.4.116,5600 (%%) ~/~/ to set TCP server address and port
25.1	271
33.2	272
	273
25.1	274	[[image:image-20220907171221-15.png]]
	275
33.2	276
	277
25.1	278	[[image:image-20220907171221-16.png]]
	279
	280
	281
33.2	282
27.1	283	=== 2.2.8 Change Update Interval ===
25.1	284
33.2	285
25.1	286	User can use below command to change the uplink interval.
	287
33.2	288	* (% style="color:#037691" %)AT+TDC=7200 (%%) ~/~/ Set Update Interval to 7200s (2 hour)
25.1	289
	290
29.1	291
33.2	292	(% style="color:red" %)NOTE: By default, the device will send an uplink message every 2 hour. Each Uplink Include 8 set of records in this 2 hour (15 minute interval / record).
	293
	294
	295
26.1	296	== 2.3 Uplink Payload ==
25.1	297
33.2	298
25.1	299	In this mode, uplink payload includes 87 bytes in total by default.
	300
	301	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.
	302
	303
33.2	304	(% border="1" style="background-color:#ffffcc; color:green; width:1251px" %)
	305	\|(% style="width:96px" %)Size(bytes)\|(% style="width:82px" %)8\|(% style="width:42px" %)2\|(% style="width:48px" %)2\|(% style="width:124px" %)1\|(% style="width:58px" %)1\|(% style="width:82px" %)1\|(% style="width:113px" %)2\|(% style="width:134px" %)2\|(% style="width:100px" %)4\|(% style="width:137px" %)2\|(% style="width:110px" %)2\|(% style="width:122px" %)4
	306	\|(% style="width:96px" %)Value\|(% style="width:82px" %)Device ID\|(% style="width:42px" %)Ver\|(% style="width:48px" %)BAT\|(% style="width:124px" %)Signal Strength\|(% style="width:58px" %)MOD\|(% style="width:82px" %)Interrupt\|(% style="width:113px" %)Leaf moisture\|(% style="width:134px" %)Leaf Temperature\|(% style="width:100px" %)Time stamp\|(% style="width:137px" %)Leaf Temperature\|(% style="width:110px" %)Leaf moisture\|(% style="width:122px" %)Time stamp .....
	307
25.1	308	If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NLMS01 uplink data.
	309
33.2	310
25.1	311	[[image:image-20220907171221-17.png]]
	312
33.2	313
25.1	314	The payload is ASCII string, representative same HEX:
	315
30.1	316	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:blue" %)0225010b6315537b010b0226631550fb010e022663154d7701110225631549f1011502246315466b01190223631542e5011d022163153f62011e022163153bde011e022163153859(%%) where:
25.1	317
30.1	318	* (% style="color:red" %)Device ID: 0xf868411056754138 = f868411056754138
	319	* (% style="color:blue" %)Version: 0x0064=100=1.0.0
	320	* (% style="color:green" %)BAT: 0x0c78 = 3192 mV = 3.192V
	321	* (% style="color:red" %)Singal: 0x17 = 23
	322	* (% style="color:blue" %)Mod: 0x01 = 1
	323	* (% style="color:green" %)Interrupt: 0x00= 0
25.1	324	* Leaf moisture: 0x0225= 549 = 54.9%
	325	* Leaf Temperature:0x010B =267=26.7 °C
31.1	326	* Time stamp : 0x6315537b =1662342011 ([[Unix Epoch Time>>https://www.epochconverter.com/]])
25.1	327	* Leaf Temperature, Leaf moisture,Time stamp : 010b0226631550fb
30.1	328	* (% style="color:blue" %)8 sets of recorded data: Leaf Temperature, Leaf moisture,Time stamp : 010e022663154d77,.......
25.1	329
33.2	330
	331
	332
26.1	333	== 2.4 Payload Explanation and Sensor Interface ==
25.1	334
33.3	335
27.1	336	=== 2.4.1 Device ID ===
25.1	337
33.3	338
25.1	339	By default, the Device ID equal to the last 15 bits of IMEI.
	340
33.4	341	User can use (% style="color:#037691" %)AT+DEUI(%%) to set Device ID
25.1	342
33.3	343
33.4	344	(% style="color:blue" %)Example:
25.1	345
	346	AT+DEUI=868411056754138
	347
	348	The Device ID is stored in a none-erase area, Upgrade the firmware or run AT+FDR won't erase Device ID.
	349
33.3	350
	351
27.1	352	=== 2.4.2 Version Info ===
25.1	353
33.3	354
25.1	355	Specify the software version: 0x64=100, means firmware version 1.00.
	356
	357	For example: 0x00 64 : this device is NLMS01 with firmware version 1.0.0.
	358
33.3	359
	360
27.1	361	=== 2.4.3 Battery Info ===
25.1	362
33.3	363
25.1	364	Check the battery voltage for NLMS01.
	365
	366	Ex1: 0x0B45 = 2885mV
	367
	368	Ex2: 0x0B49 = 2889mV
	369
33.3	370
	371
27.1	372	=== 2.4.4 Signal Strength ===
25.1	373
33.3	374
25.1	375	NB-IoT Network signal Strength.
	376
	377
33.4	378	(% style="color:blue" %)Ex1: 0x1d = 29
	379
25.1	380	0 -113dBm or less
	381
	382	1 -111dBm
	383
	384	2...30 -109dBm... -53dBm
	385
	386	31 -51dBm or greater
	387
	388	99 Not known or not detectable
	389
33.3	390
	391
27.1	392	=== 2.4.5 Leaf moisture ===
25.1	393
33.3	394
33.4	395	Get the moisture of the (% style="color:#037691" %)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.
25.1	396
33.4	397	For example, if the data you get from the register is (% style="color:#037691" %)__0x05 0xDC__(%%), the moisture content in the (% style="color:#037691" %)Leaf(%%) is
25.1	398
33.4	399	(% style="color:blue" %)0229(H) = 549(D) /100 = 54.9.
25.1	400
33.3	401
	402
27.1	403	=== 2.4.6 Leaf Temperature ===
25.1	404
33.3	405
33.4	406	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 (% style="color:#037691" %)__0x09 0xEC__(%%), the temperature content in the (% style="color:#037691" %)Leaf (%%)is
25.1	407
33.4	408	(% style="color:blue" %)Example:
25.1	409
33.4	410	If payload is 0105H: ((0x0105 & 0x8000)>>15 === 0),temp = 0105(H)/10 = 26.1 °C
25.1	411
33.4	412	If payload is FF7EH: ((FF7E & 0x8000)>>15 ===1),temp = (FF7E(H)-FFFF(H))/10 = -12.9 °C
25.1	413
33.3	414
	415
27.1	416	=== 2.4.7 Timestamp ===
25.1	417
33.3	418
25.1	419	Time stamp : 0x6315537b =1662342011
	420
	421	Convert Unix timestamp to time 2022-9-5 9:40:11.
	422
33.3	423
33.4	424
27.1	425	=== 2.4.8 Digital Interrupt ===
25.1	426
33.3	427
33.4	428	Digital Interrupt refers to pin (% style="color:#037691" %)GPIO_EXTI(%%), and there are different trigger methods. When there is a trigger, the NLMS01 will send a packet to the server.
25.1	429
	430	The command is:
	431
33.4	432	(% 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]]).
25.1	433
	434	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.
	435
	436	Example:
	437
	438	0x(00): Normal uplink packet.
	439
	440	0x(01): Interrupt Uplink Packet.
	441
33.3	442
	443
27.1	444	=== 2.4.9 +5V Output ===
25.1	445
33.3	446
25.1	447	NLMS01 will enable +5V output before all sampling and disable the +5v after all sampling.
	448
	449	The 5V output time can be controlled by AT Command.
	450
33.4	451	(% style="color:blue" %)AT+5VT=1000
25.1	452
	453	Means set 5V valid time to have 1000ms. So the real 5V output will actually have 1000ms + sampling time for other sensors.
	454
	455
33.3	456
26.1	457	== 2.5 Downlink Payload ==
25.1	458
33.3	459
25.1	460	By default, NLMS01 prints the downlink payload to console port.
	461
	462	[[image:image-20220907171221-18.png]]
	463
33.3	464
33.4	465	(% style="color:blue" %)Examples:
25.1	466
	467
33.4	468	* (% style="color:#037691" %)Set TDC
	469
25.1	470	If the payload=0100003C, it means set the END Node's TDC to 0x00003C=60(S), while type code is 01.
	471
	472	Payload: 01 00 00 1E TDC=30S
	473
	474	Payload: 01 00 00 3C TDC=60S
	475
	476
33.4	477
	478	* (% style="color:#037691" %)Reset
	479
25.1	480	If payload = 0x04FF, it will reset the NLMS01
	481
	482
33.4	483
	484	* (% style="color:#037691" %)INTMOD
	485
25.1	486	Downlink Payload: 06000003, Set AT+INTMOD=3
	487
33.3	488
	489
26.1	490	== 2.6 LED Indicator ==
25.1	491
33.3	492
25.1	493	The NLMS01 has an internal LED which is to show the status of different state.
	494
	495	* When power on, NLMS01 will detect if sensor probe is connected, if probe detected, LED will blink four times. (no blinks in this step is no probe)
	496	* Then the LED will be on for 1 second means device is boot normally.
	497	* After NLMS01 join NB-IoT network. The LED will be ON for 3 seconds.
	498	* For each uplink probe, LED will be on for 500ms.
	499
	500
33.3	501
	502
	503	== 2.7 Installation ==
	504
	505
25.1	506	NLMS01 probe has two sides. The side without words are the sense side. Please be ware when install the sensor.
	507
33.3	508
25.1	509	[[image:image-20220907171221-19.png]]
	510
	511
	512
33.3	513	== 2.8 Moisture and Temperature alarm function ==
25.1	514
33.3	515
33.4	516	(% style="color:blue" %)➢ AT Command:
33.3	517
33.4	518	(% style="color:#037691" %)AT+ HUMALARM =min,max
33.3	519
25.1	520	² When min=0, and max≠0, Alarm higher than max
	521
	522	² When min≠0, and max=0, Alarm lower than min
	523
	524	² When min≠0 and max≠0, Alarm higher than max or lower than min
	525
	526
33.4	527	(% style="color:blue" %)Example:
33.3	528
25.1	529	AT+ HUMALARM =50,60 ~/~/ Alarm when moisture lower than 50.
	530
	531	AT+ TEMPALARM=min,max
	532
	533	² When min=0, and max≠0, Alarm higher than max
	534
	535	² When min≠0, and max=0, Alarm lower than min
	536
	537	² When min≠0 and max≠0, Alarm higher than max or lower than min
	538
	539
33.4	540	(% style="color:blue" %)Example:
33.3	541
25.1	542	AT+ TEMPALARM=20,30 ~/~/ Alarm when temperature lower than 20.
	543
	544
	545
33.3	546	== 2.9 Set the number of data to be uploaded and the recording time ==
25.1	547
	548
33.4	549	(% style="color:blue" %)➢ AT Command:
25.1	550
33.4	551	* (% style="color:#037691" %)AT+TR=900 (%%) ~/~/ The unit is seconds, and the default is to record data once every 900 seconds.( The minimum can be set to 180 seconds)
	552	* (% style="color:#037691" %)AT+NOUD=8 (%%)~/~/ The device uploads 8 sets of recorded data by default. Up to 32 sets of record data can be uploaded.
25.1	553
	554
	555
33.3	556
	557	== 2.10 Read or Clear cached data ==
	558
	559
33.4	560	(% style="color:blue" %)➢ AT Command:
33.3	561
33.4	562	* (% style="color:#037691" %)AT+CDP (%%) ~/~/ Read cached data
	563	* (% style="color:#037691" %)AT+CDP=0 (%%) ~/~/ Clear cached data
33.3	564
	565
	566
25.1	567	[[image:image-20220907171221-20.png]]
	568
	569
	570
26.1	571	== 2.11 Firmware Change Log ==
25.1	572
33.3	573
25.1	574	Download URL & Firmware Change log: [[https:~~/~~/www.dropbox.com/sh/1zmcakvbkf24f8x/AACmq2dZ3iRB9F1nVWeEB9Moa?dl=0>>url:https://www.dropbox.com/sh/1zmcakvbkf24f8x/AACmq2dZ3iRB9F1nVWeEB9Moa?dl=0]]
	575
	576	Upgrade Instruction: [[Upgrade Firmware>>path:#H5.1200BHowtoUpgradeFirmware]]
	577
33.3	578
	579
26.1	580	== 2.12 Battery Analysis ==
25.1	581
33.3	582
27.1	583	=== 2.12.1 Battery Type ===
25.1	584
33.3	585
25.1	586	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.
	587
	588	The battery is designed to last for several years depends on the actually use environment and update interval.
	589
	590	The battery related documents as below:
	591
	592	* [[Battery Dimension>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
	593	* [[Lithium-Thionyl Chloride Battery datasheet>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
	594	* [[Lithium-ion Battery-Capacitor datasheet>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
	595
	596	[[image:image-20220907171221-21.png]]
	597
33.3	598
	599
27.1	600	=== 2.12.2 Power consumption Analyze ===
25.1	601
33.3	602
25.1	603	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.
	604
	605	Instruction to use as below:
	606
33.4	607	(% 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/]]
25.1	608
33.4	609	(% style="color:blue" %)Step 2: (%%) Open it and choose
25.1	610
	611	* Product Model
	612	* Uplink Interval
	613	* Working Mode
	614
	615	And the Life expectation in difference case will be shown on the right.
	616
	617	[[image:image-20220907171221-22.jpeg]]
	618
33.3	619
27.1	620	=== 2.12.3 Battery Note ===
25.1	621
33.3	622
25.1	623	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.
	624
33.3	625
	626
27.1	627	=== 2.12.4 Replace the battery ===
25.1	628
33.3	629
25.1	630	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).
	631
33.3	632
	633
26.1	634	= 3. Access NB-IoT Module =
25.1	635
33.3	636
25.1	637	Users can directly access the AT command set of the NB-IoT module.
	638
	639	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/]]
	640
33.3	641
25.1	642	[[image:image-20220907171221-23.png]]
	643
33.3	644
	645
26.1	646	= 4. Using the AT Commands =
25.1	647
33.3	648
27.1	649	== 4.1 Access AT Commands ==
25.1	650
33.3	651
25.1	652	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]]
	653
	654	AT+<CMD>? : Help on <CMD>
	655
	656	AT+<CMD> : Run <CMD>
	657
	658	AT+<CMD>=<value> : Set the value
	659
	660	AT+<CMD>=? : Get the value
	661
33.3	662
33.4	663	(% style="color:#037691" %)General Commands
25.1	664
	665	AT : Attention
	666
	667	AT? : Short Help
	668
	669	ATZ : MCU Reset
	670
	671	AT+TDC : Application Data Transmission Interval
	672
	673	AT+CFG : Print all configurations
	674
	675	AT+CFGMOD : Working mode selection
	676
	677	AT+INTMOD : Set the trigger interrupt mode
	678
	679	AT+5VT : Set extend the time of 5V power
	680
	681	AT+PRO : Choose agreement
	682
	683	AT+RXDL : Extend the sending and receiving time
	684
	685	AT+SERVADDR : Server Address
	686
32.1	687	AT+APN : Get or set the APN
	688
	689	AT+FBAND : Get or Set whether to automatically modify the frequency band
	690
	691	AT+DNSCFG : Get or Set DNS Server
	692
	693	AT+GETSENSORVALUE : Returns the current sensor measurement
	694
25.1	695	AT+TR : Get or Set record time"
	696
	697	AT+NOUD : Get or Set the number of data to be uploaded
	698
	699	AT+CDP : Read or Clear cached data
	700
	701	AT+TEMPALARM : Get or Set alarm of temp
	702
	703	AT+HUMALARM : Get or Set alarm of PH
	704
	705
33.4	706	(% style="color:#037691" %)COAP Management
25.1	707
	708	AT+URI : Resource parameters
	709
33.3	710
33.4	711	(% style="color:#037691" %)UDP Management
25.1	712
	713	AT+CFM : Upload confirmation mode (only valid for UDP)
	714
33.3	715
33.4	716	(% style="color:#037691" %)MQTT Management
25.1	717
	718	AT+CLIENT : Get or Set MQTT client
	719
	720	AT+UNAME : Get or Set MQTT Username
	721
	722	AT+PWD : Get or Set MQTT password
	723
	724	AT+PUBTOPIC : Get or Set MQTT publish topic
	725
	726	AT+SUBTOPIC : Get or Set MQTT subscription topic
	727
33.3	728
33.4	729	(% style="color:#037691" %)Information
25.1	730
	731	AT+FDR : Factory Data Reset
	732
	733	AT+PWORD : Serial Access Password
	734
33.3	735
	736
26.1	737	= 5. FAQ =
25.1	738
33.3	739
27.1	740	== 5.1 How to Upgrade Firmware ==
25.1	741
33.3	742
25.1	743	User can upgrade the firmware for 1) bug fix, 2) new feature release.
	744
	745	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]]
	746
	747
33.4	748	(% style="color:red" %)Notice, NLMS01 and LLMS01 share the same mother board. They use the same connection and method to update.
33.3	749
	750
33.4	751
26.1	752	= 6. Trouble Shooting =
25.1	753
33.3	754
27.1	755	== 6.1 Connection problem when uploading firmware ==
25.1	756
33.3	757
25.1	758	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]]
	759
33.3	760
	761
27.1	762	== 6.2 AT Command input doesn't work ==
25.1	763
33.3	764
33.4	765	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.
25.1	766
33.3	767
	768
26.1	769	= 7. Order Info =
25.1	770
33.3	771
25.1	772	Part Number: NLMS01
	773
33.3	774
	775
26.1	776	= 8. Packing Info =
25.1	777
33.3	778
33.4	779	(% style="color:#037691" %)Package Includes:
25.1	780
	781	* NLMS01 NB-IoT Leaf Moisture Sensor x 1
	782
33.4	783	(% style="color:#037691" %)Dimension and weight:
25.1	784
	785	* Device Size: cm
	786	* Device Weight: g
	787	* Package Size / pcs : cm
	788	* Weight / pcs : g
	789
33.3	790
	791
26.1	792	= 9. Support =
25.1	793
33.3	794
25.1	795	* 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.
	796	* 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]]
	797
	798

Wiki source code of NLMS01-NB-IoT Leaf Moisture Sensor User Manual

Applications