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

Version 40.1 by Bei Jinggeng on 2024/03/30 17:56

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

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

Applications

Navigation