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

Version 38.20 by Xiaoling on 2023/05/24 08:56

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

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

Applications