Wiki source code of NDDS75 NB-IoT Distance Detect Sensor User Manual

Version 94.1 by Xiaoling on 2022/07/09 10:16

version	line-number	content
74.2	1	(% style="text-align:center" %)
	2	[[image:image-20220709085040-1.png\|\|height="542" width="524"]]
1.1	3
	4
	5
35.25	6
	7
35.4	8	Table of Contents:
1.1	9
	10
	11
	12
	13
31.17	14
65.3	15
44.2	16	= 1. Introduction =
1.1	17
67.2	18	== 1.1 What is NDDS75 Distance Detection Sensor ==
1.1	19
12.2	20	(((
35.4	21
	22
65.9	23	(((
68.2	24	The Dragino NDDS75 is a (% style="color:blue" %)NB-IoT Distance Detection Sensor(%%) for Internet of Things solution. It is designed to measure the distance between the sensor and a flat object. The distance detection sensor is a module that uses ultrasonic sensing technology for distance measurement, and temperature compensation is performed internally to improve the reliability of data.
	25	\\The NDDS75 can be applied to scenarios such as horizontal distance measurement, liquid level measurement, parking management system, object proximity and presence detection, intelligent trash can management system, robot obstacle avoidance, automatic control, sewer, bottom water level monitoring, etc. It detects the distance between the measured object and the sensor, and uploads the value via wireless to IoT Server via NB-IoT Network.
	26	\\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.
	27	\\NDDS75 supports different uplink methods include (% style="color:blue" %)TCP, MQTT, UDP and CoAP (%%)for different application requirement.
	28	\\NDDS75 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)
	29	\\To use NDDS75, user needs to check if there is NB-IoT coverage in local area and with the bands NDDS75 supports. If the local operate support it, user needs to get a NB-IoT SIM card from local operator and install NDDS75 to get NB-IoT network connection.
65.9	30	)))
4.2	31
42.2	32
12.2	33	)))
4.2	34
12.2	35	[[image:1654503236291-817.png]]
4.2	36
	37
75.2	38	[[image:1657327959271-447.png]]
4.2	39
	40
	41
65.3	42	== 1.2 Features ==
13.3	43
75.3	44
44.2	45	* NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD
75.3	46	* Ultra low power consumption
	47	* Distance Detection by Ultrasonic technology
	48	* Flat object range 280mm - 7500mm
	49	* Accuracy: ±(1cm+S*0.3%) (S: Distance)
	50	* Cable Length: 25cm
4.2	51	* AT Commands to change parameters
	52	* Uplink on periodically
	53	* Downlink to change configure
	54	* IP66 Waterproof Enclosure
44.2	55	* Micro SIM card slot for NB-IoT SIM
	56	* 8500mAh Battery for long term use
4.2	57
91.2	58
44.2	59	== 1.3 Specification ==
	60
	61
	62	(% style="color:#037691" %)Common DC Characteristics:
	63
	64	* Supply Voltage: 2.1v ~~ 3.6v
	65	* Operating Temperature: -40 ~~ 85°C
	66
	67	(% style="color:#037691" %)NB-IoT Spec:
	68
	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
	75
75.3	76	(% style="color:#037691" %)Battery:
4.2	77
75.3	78	* Li/SOCI2 un-chargeable battery
	79	* Capacity: 8500mAh
	80	* Self Discharge: <1% / Year @ 25°C
	81	* Max continuously current: 130mA
	82	* Max boost current: 2A, 1 second
14.2	83
75.3	84	(% style="color:#037691" %)Power Consumption
4.2	85
75.3	86	* STOP Mode: 10uA @ 3.3v
91.3	87	* Max transmit power: [[350mA@3.3v>>mailto:350mA@3.3v]]
75.3	88
91.3	89
	90
44.2	91	== 1.4 Applications ==
4.2	92
75.4	93	* Smart Buildings & Home Automation
	94	* Logistics and Supply Chain Management
	95	* Smart Metering
4.2	96	* Smart Agriculture
75.4	97	* Smart Cities
	98	* Smart Factory
4.2	99
15.6	100	(% class="wikigeneratedid" id="H200B1.5FirmwareChangelog" %)
	101
4.2	102
75.4	103
	104
44.2	105	== 1.5 Pin Definitions ==
15.6	106
	107
76.2	108	[[image:1657328609906-564.png]]
4.2	109
14.3	110
	111
81.2	112	= 2. Use NDDS75 to communicate with IoT Server =
14.3	113
45.2	114	== 2.1 How it works ==
14.3	115
15.3	116	(((
77.2	117	The NDDS75 is equipped with a NB-IoT module, the pre-loaded firmware in NDDS75 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 NDDS75.
15.3	118	)))
4.2	119
45.2	120
15.3	121	(((
77.2	122	The diagram below shows the working flow in default firmware of NDDS75:
15.3	123	)))
4.2	124
77.2	125	(((
	126
	127	)))
4.2	128
77.2	129	[[image:1657328659945-416.png]]
	130
45.2	131	(((
	132
	133	)))
4.2	134
45.2	135
81.2	136	== 2.2 Configure the NDDS75 ==
4.2	137
48.2	138
45.4	139	=== 2.2.1 Test Requirement ===
4.2	140
65.10	141	(((
81.2	142	To use NDDS75 in your city, make sure meet below requirements:
65.10	143	)))
4.2	144
45.4	145	* Your local operator has already distributed a NB-IoT Network there.
	146	* The local NB-IoT network used the band that NSE01 supports.
	147	* Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
4.2	148
48.2	149	(((
81.2	150	Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8. The NDDS75 will use CoAP((% style="color:red" %)120.24.4.116:5683)(%%) or raw UDP((% style="color:red" %)120.24.4.116:5601)(%%) or MQTT((% style="color:red" %)120.24.4.116:1883)(%%)or TCP((% style="color:red" %)120.24.4.116:5600)(%%)protocol to send data to the test server
48.2	151	)))
4.2	152
	153
81.2	154	[[image:1657328756309-230.png]]
4.2	155
	156
	157
45.5	158	=== 2.2.2 Insert SIM card ===
4.2	159
65.11	160	(((
45.4	161	Insert the NB-IoT Card get from your provider.
65.11	162	)))
4.2	163
65.11	164	(((
45.4	165	User need to take out the NB-IoT module and insert the SIM card like below:
65.11	166	)))
4.2	167
	168
81.2	169	[[image:1657328884227-504.png]]
4.2	170
	171
48.2	172
81.2	173	=== 2.2.3 Connect USB – TTL to NDDS75 to configure it ===
4.2	174
48.2	175	(((
	176	(((
81.2	177	User need to configure NDDS75 via serial port to set the (% style="color:blue" %)Server Address / Uplink Topic (%%)to define where and how-to uplink packets. NDDS75 support AT Commands, user can use a USB to TTL adapter to connect to NDDS75 and use AT Commands to configure it, as below.
48.2	178	)))
	179	)))
19.2	180
81.2	181	[[image:image-20220709092052-2.png]]
4.2	182
48.2	183	Connection:
4.2	184
45.6	185	(% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND
4.2	186
45.6	187	(% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD
4.2	188
45.6	189	(% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD
4.2	190
	191
45.4	192	In the PC, use below serial tool settings:
	193
57.4	194	* Baud: (% style="color:green" %)9600
48.2	195	* Data bits: (% style="color:green" %)8(%%)
	196	* Stop bits: (% style="color:green" %)1
57.4	197	* Parity: (% style="color:green" %)None
48.2	198	* Flow Control: (% style="color:green" %)None
45.4	199
48.2	200	(((
81.2	201	Make sure the switch is in FLASH position, then power on device by connecting the jumper on NDDS75. NDDS75 will output system info once power on as below, we can enter the (% style="color:green" %)password: 12345678(%%) to access AT Command input.
48.2	202	)))
45.4	203
81.2	204	[[image:1657329814315-101.png]]
45.4	205
65.12	206	(((
81.2	207	(% style="color:red" %)Note: the valid AT Commands can be found at: (%%)[[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/]]
65.12	208	)))
45.4	209
	210
	211
48.2	212	=== 2.2.4 Use CoAP protocol to uplink data ===
45.4	213
56.2	214	(% 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/>>http://wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/]]
45.4	215
	216
50.2	217	Use below commands:
45.4	218
48.2	219	* (% style="color:blue" %)AT+PRO=1 (%%) ~/~/ Set to use CoAP protocol to uplink
	220	* (% style="color:blue" %)AT+SERVADDR=120.24.4.116,5683 (%%)~/~/ to set CoAP server address and port
	221	* (% style="color:blue" %)AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" (%%) ~/~/Set COAP resource path
45.4	222
	223	For parameter description, please refer to AT command set
	224
86.2	225	[[image:1657330452568-615.png]]
45.4	226
	227
86.2	228	After configure the server address and (% style="color:green" %)reset the device(%%) (via AT+ATZ ), NDDS75 will start to uplink sensor values to CoAP server.
45.4	229
86.2	230	[[image:1657330472797-498.png]]
45.4	231
	232
50.2	233
45.6	234	=== 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
45.4	235
	236
48.2	237	* (% style="color:blue" %)AT+PRO=2 (%%) ~/~/ Set to use UDP protocol to uplink
	238	* (% style="color:blue" %)AT+SERVADDR=120.24.4.116,5601 (%%) ~/~/ to set UDP server address and port
	239	* (% style="color:blue" %)AT+CFM=1 (%%) ~/~/If the server does not respond, this command is unnecessary
45.4	240
86.2	241	[[image:1657330501006-241.png]]
45.4	242
	243
86.2	244	[[image:1657330533775-472.png]]
45.4	245
52.3	246
86.2	247
45.7	248	=== 2.2.6 Use MQTT protocol to uplink data ===
45.4	249
	250
54.3	251	* (% style="color:blue" %)AT+PRO=3 (%%) ~/~/Set to use MQTT protocol to uplink
	252	* (% style="color:blue" %)AT+SERVADDR=120.24.4.116,1883 (%%) ~/~/Set MQTT server address and port
	253	* (% style="color:blue" %)AT+CLIENT=CLIENT (%%)~/~/Set up the CLIENT of MQTT
57.2	254	* (% style="color:blue" %)AT+UNAME=UNAME (%%)~/~/Set the username of MQTT
	255	* (% style="color:blue" %)AT+PWD=PWD (%%)~/~/Set the password of MQTT
89.2	256	* (% style="color:blue" %)AT+PUBTOPIC=NDDS75_PUB (%%)~/~/Set the sending topic of MQTT
	257	* (% style="color:blue" %)AT+SUBTOPIC=NDDS75_SUB (%%) ~/~/Set the subscription topic of MQTT
45.4	258
54.2	259	[[image:1657249978444-674.png]]
45.4	260
54.2	261
89.2	262	[[image:1657330723006-866.png]]
54.2	263
45.4	264
54.3	265	(((
45.4	266	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.
54.3	267	)))
45.4	268
	269
54.3	270
45.7	271	=== 2.2.7 Use TCP protocol to uplink data ===
45.4	272
	273
56.2	274	* (% style="color:blue" %)AT+PRO=4 (%%) ~/~/ Set to use TCP protocol to uplink
48.2	275	* (% style="color:blue" %)AT+SERVADDR=120.24.4.116,5600 (%%) ~/~/ to set TCP server address and port
45.4	276
89.2	277	[[image:image-20220709093918-1.png]]
45.4	278
	279
89.2	280	[[image:image-20220709093918-2.png]]
45.4	281
57.6	282
89.2	283
45.7	284	=== 2.2.8 Change Update Interval ===
45.4	285
48.2	286	User can use below command to change the (% style="color:green" %)uplink interval.
45.4	287
56.3	288	* (% style="color:blue" %)AT+TDC=600 (%%)~/~/ Set Update Interval to 600s
45.4	289
56.3	290	(((
48.2	291	(% style="color:red" %)NOTE:
56.3	292	)))
45.4	293
56.3	294	(((
45.7	295	(% style="color:red" %)1. By default, the device will send an uplink message every 1 hour.
56.3	296	)))
45.4	297
	298
	299
57.2	300	== 2.3 Uplink Payload ==
4.2	301
90.2	302	In this mode, uplink payload includes in total 14 bytes
32.9	303
90.2	304
57.2	305	(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:510px" %)
65.12	306	\|=(% style="width: 60px;" %)(((
57.2	307	Size(bytes)
90.2	308	)))\|=(% style="width: 50px;" %)6\|=(% style="width: 25px;" %)2\|=(% style="width: 25px;" %)2\|=(% style="width: 70px;" %)1\|=(% style="width: 60px;" %)2\|=(% style="width: 50px;" %)1
	309	\|(% style="width:97px" %)Value\|(% style="width:83px" %)[[Device ID>>\|\|anchor="H2.4.1A0A0DeviceID"]]\|(% style="width:41px" %)[[Ver>>\|\|anchor="H2.4.2A0VersionInfo"]]\|(% style="width:46px" %)[[BAT>>\|\|anchor="H2.4.3A0BatteryInfo"]]\|(% style="width:123px" %)[[Signal Strength>>\|\|anchor="H2.4.4A0SignalStrength"]]\|(% style="width:108px" %)[[Distance (unit: mm)>>\|\|anchor="H2.4.5A0SoilMoisture"]]\|(% style="width:80px" %)[[Interrupt>>\|\|anchor="H2.4.8A0DigitalInterrupt"]]
57.2	310
65.13	311	(((
90.2	312	If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS751 uplink data.
65.13	313	)))
57.2	314
	315
90.2	316	[[image:1657331036973-987.png]]
57.2	317
90.2	318	(((
57.2	319	The payload is ASCII string, representative same HEX:
90.2	320	)))
57.2	321
90.2	322	(((
	323	0x72403155615900640c6c19029200 where:
	324	)))
57.2	325
90.2	326	* (((
	327	Device ID: 0x724031556159 = 724031556159
	328	)))
	329	* (((
	330	Version: 0x0064=100=1.0.0
	331	)))
57.2	332
90.2	333	* (((
	334	BAT: 0x0c6c = 3180 mV = 3.180V
	335	)))
	336	* (((
	337	Signal: 0x19 = 25
	338	)))
	339	* (((
	340	Distance: 0x0292= 658 mm
	341	)))
	342	* (((
	343	Interrupt: 0x00 = 0
	344	)))
57.2	345
90.2	346
57.3	347	== 2.4 Payload Explanation and Sensor Interface ==
4.2	348
57.7	349
57.5	350	=== 2.4.1 Device ID ===
4.2	351
65.13	352	(((
57.3	353	By default, the Device ID equal to the last 6 bytes of IMEI.
65.13	354	)))
4.2	355
65.13	356	(((
57.4	357	User can use (% style="color:blue" %)AT+DEUI(%%) to set Device ID
65.13	358	)))
4.2	359
65.13	360	(((
57.3	361	Example:
65.13	362	)))
4.2	363
65.13	364	(((
57.3	365	AT+DEUI=A84041F15612
65.13	366	)))
4.2	367
65.13	368	(((
91.1	369	The Device ID is stored in a none-erase area, Upgrade the firmware or run AT+FDR won't erase Device ID.
65.13	370	)))
22.2	371
4.2	372
	373
57.5	374	=== 2.4.2 Version Info ===
	375
65.13	376	(((
57.3	377	Specify the software version: 0x64=100, means firmware version 1.00.
65.13	378	)))
4.2	379
65.13	380	(((
91.1	381	For example: 0x00 64 : this device is NDDS75 with firmware version 1.0.0.
65.13	382	)))
4.2	383
	384
57.3	385
57.5	386	=== 2.4.3 Battery Info ===
22.2	387
32.10	388	(((
4.2	389	Check the battery voltage for LSE01.
32.10	390	)))
4.2	391
32.10	392	(((
4.2	393	Ex1: 0x0B45 = 2885mV
32.10	394	)))
4.2	395
32.10	396	(((
4.2	397	Ex2: 0x0B49 = 2889mV
32.10	398	)))
4.2	399
	400
	401
57.6	402	=== 2.4.4 Signal Strength ===
4.2	403
65.13	404	(((
57.6	405	NB-IoT Network signal Strength.
65.13	406	)))
57.6	407
65.13	408	(((
57.6	409	Ex1: 0x1d = 29
65.13	410	)))
57.6	411
65.13	412	(((
57.6	413	(% style="color:blue" %)0(%%) -113dBm or less
65.13	414	)))
57.6	415
65.13	416	(((
57.6	417	(% style="color:blue" %)1(%%) -111dBm
65.13	418	)))
57.6	419
65.13	420	(((
57.6	421	(% style="color:blue" %)2...30(%%) -109dBm... -53dBm
65.13	422	)))
57.6	423
65.13	424	(((
57.6	425	(% style="color:blue" %)31 (%%) -51dBm or greater
65.13	426	)))
57.6	427
65.13	428	(((
57.6	429	(% style="color:blue" %)99 (%%) Not known or not detectable
65.13	430	)))
57.6	431
	432
	433
	434	=== 2.4.5 Soil Moisture ===
	435
91.1	436	Get the distance. Flat object range 280mm - 7500mm.
4.2	437
91.1	438	For example, if the data you get from the register is __0x0B 0x05__, the distance between the sensor and the measured object is
4.2	439
32.10	440	(((
	441	(((
91.4	442	(% style="color:blue" %) 0B05(H) = 2821(D) = 2821mm.
32.10	443	)))
32.11	444	)))
4.2	445
32.11	446	(((
23.2	447
	448	)))
4.2	449
23.2	450	(((
	451
	452	)))
	453
91.1	454	=== 2.4.6 Digital Interrupt ===
23.2	455
65.15	456	(((
91.1	457	Digital Interrupt refers to pin (% style="color:blue" %)GPIO_EXTI(%%), and there are different trigger methods. When there is a trigger, the NDDS75 will send a packet to the server.
65.15	458	)))
4.2	459
65.15	460	(((
57.6	461	The command is:
65.15	462	)))
4.2	463
65.15	464	(((
57.8	465	(% 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]]).
65.15	466	)))
4.2	467
	468
65.15	469	(((
65.6	470	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.
65.15	471	)))
4.2	472
	473
65.15	474	(((
57.6	475	Example:
65.15	476	)))
4.2	477
65.15	478	(((
57.6	479	0x(00): Normal uplink packet.
65.15	480	)))
4.2	481
65.15	482	(((
57.6	483	0x(01): Interrupt Uplink Packet.
65.15	484	)))
23.2	485
4.2	486
	487
91.1	488	=== 2.4.7 +5V Output ===
4.2	489
65.16	490	(((
91.1	491	NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling.
65.16	492	)))
4.2	493
57.6	494
65.16	495	(((
57.6	496	The 5V output time can be controlled by AT Command.
65.16	497	)))
57.6	498
65.16	499	(((
57.7	500	(% style="color:blue" %)AT+5VT=1000
65.16	501	)))
57.6	502
65.16	503	(((
57.6	504	Means set 5V valid time to have 1000ms. So the real 5V output will actually have 1000ms + sampling time for other sensors.
65.16	505	)))
57.6	506
	507
	508
58.2	509	== 2.5 Downlink Payload ==
4.2	510
92.2	511	By default, NDDS75 prints the downlink payload to console port.
4.2	512
92.2	513	[[image:image-20220709100028-1.png]]
4.2	514
	515
32.14	516	(((
40.4	517	(% style="color:blue" %)Examples:
32.14	518	)))
4.2	519
32.14	520	(((
	521
	522	)))
4.2	523
32.14	524	* (((
40.4	525	(% style="color:blue" %)Set TDC
32.14	526	)))
4.2	527
32.14	528	(((
60.2	529	If the payload=0100003C, it means set the END Node's TDC to 0x00003C=60(S), while type code is 01.
32.14	530	)))
4.2	531
32.14	532	(((
4.2	533	Payload: 01 00 00 1E TDC=30S
32.14	534	)))
4.2	535
32.14	536	(((
4.2	537	Payload: 01 00 00 3C TDC=60S
32.14	538	)))
4.2	539
32.14	540	(((
	541
	542	)))
4.2	543
32.14	544	* (((
40.4	545	(% style="color:blue" %)Reset
32.14	546	)))
4.2	547
32.14	548	(((
92.2	549	If payload = 0x04FF, it will reset the NDDS75
32.14	550	)))
4.2	551
	552
60.2	553	* (% style="color:blue" %)INTMOD
4.2	554
65.17	555	(((
60.2	556	Downlink Payload: 06000003, Set AT+INTMOD=3
65.17	557	)))
4.2	558
	559
26.2	560
60.2	561	== 2.6 LED Indicator ==
26.2	562
4.2	563
92.2	564	The NDDS75 has an internal LED which is to show the status of different state.
4.2	565
92.2	566
	567	* When power on, NDDS75 will detect if sensor probe is connected, if probe detected, LED will blink four times. (no blinks in this step is no probe)
60.2	568	* Then the LED will be on for 1 second means device is boot normally.
92.2	569	* After NDDS75 join NB-IoT network. The LED will be ON for 3 seconds.
60.2	570	* For each uplink probe, LED will be on for 500ms.
92.2	571
	572	(((
	573
32.15	574	)))
4.2	575
	576
	577
92.3	578	== 2.7 Firmware Change Log ==
4.2	579
	580
92.3	581	Download URL & Firmware Change log
4.2	582
60.2	583	(((
92.3	584	[[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/Firmware/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/Firmware/]]
60.2	585	)))
4.2	586
	587
65.6	588	Upgrade Instruction: [[Upgrade_Firmware>>\|\|anchor="H5.1200BHowtoUpgradeFirmware"]]
28.5	589
4.2	590
	591
60.2	592	== 2.9 Battery Analysis ==
4.2	593
60.2	594	=== 2.9.1 Battery Type ===
4.2	595
	596
65.18	597	(((
60.2	598	The NSE01 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.
65.18	599	)))
4.2	600
	601
65.18	602	(((
62.3	603	The battery is designed to last for several years depends on the actually use environment and update interval.
65.18	604	)))
4.2	605
	606
65.18	607	(((
60.2	608	The battery related documents as below:
65.18	609	)))
4.2	610
60.2	611	* [[Battery Dimension>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
65.7	612	* [[Lithium-Thionyl Chloride Battery datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
60.2	613	* [[Lithium-ion Battery-Capacitor datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
4.2	614
29.2	615	(((
60.2	616	[[image:image-20220708140453-6.png]]
29.2	617	)))
4.2	618
	619
35.18	620
62.2	621	=== 2.9.2 Power consumption Analyze ===
4.2	622
62.3	623	(((
60.2	624	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.
62.3	625	)))
4.2	626
	627
62.3	628	(((
60.2	629	Instruction to use as below:
62.3	630	)))
4.2	631
62.3	632	(((
	633	(% 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/]]
	634	)))
4.2	635
	636
62.3	637	(((
	638	(% style="color:blue" %)Step 2: (%%) Open it and choose
	639	)))
4.2	640
62.3	641	* (((
	642	Product Model
	643	)))
	644	* (((
	645	Uplink Interval
	646	)))
	647	* (((
	648	Working Mode
	649	)))
4.2	650
62.3	651	(((
60.2	652	And the Life expectation in difference case will be shown on the right.
62.3	653	)))
4.2	654
62.2	655	[[image:image-20220708141352-7.jpeg]]
4.2	656
	657
62.2	658
60.2	659	=== 2.9.3 Battery Note ===
4.2	660
31.6	661	(((
4.2	662	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.
31.3	663	)))
4.2	664
	665
	666
60.2	667	=== 2.9.4 Replace the battery ===
31.2	668
62.2	669	(((
60.2	670	The default battery pack of NSE01 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).
62.2	671	)))
4.2	672
	673
	674
63.2	675	= 3. Access NB-IoT Module =
4.2	676
63.2	677	(((
	678	Users can directly access the AT command set of the NB-IoT module.
	679	)))
	680
	681	(((
64.2	682	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/]]
63.2	683	)))
	684
64.2	685	[[image:1657261278785-153.png]]
63.2	686
	687
	688
64.2	689	= 4. Using the AT Commands =
63.2	690
64.2	691	== 4.1 Access AT Commands ==
9.2	692
64.2	693	See this link for detail: [[http:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/NSE01/>>url:http://www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN50/]]
11.4	694
4.2	695
64.2	696	AT+<CMD>? : Help on <CMD>
4.2	697
64.2	698	AT+<CMD> : Run <CMD>
4.2	699
64.2	700	AT+<CMD>=<value> : Set the value
4.2	701
64.2	702	AT+<CMD>=? : Get the value
4.2	703
	704
11.6	705	(% style="color:#037691" %)General Commands(%%)
4.2	706
64.2	707	AT : Attention
4.2	708
64.2	709	AT? : Short Help
4.2	710
64.2	711	ATZ : MCU Reset
4.2	712
64.2	713	AT+TDC : Application Data Transmission Interval
4.2	714
64.2	715	AT+CFG : Print all configurations
4.2	716
64.2	717	AT+CFGMOD : Working mode selection
4.2	718
64.2	719	AT+INTMOD : Set the trigger interrupt mode
4.2	720
64.2	721	AT+5VT : Set extend the time of 5V power
4.2	722
64.2	723	AT+PRO : Choose agreement
4.2	724
64.2	725	AT+WEIGRE : Get weight or set weight to 0
4.2	726
64.2	727	AT+WEIGAP : Get or Set the GapValue of weight
4.2	728
64.2	729	AT+RXDL : Extend the sending and receiving time
4.2	730
64.2	731	AT+CNTFAC : Get or set counting parameters
4.2	732
64.2	733	AT+SERVADDR : Server Address
4.2	734
	735
64.2	736	(% style="color:#037691" %)COAP Management
4.2	737
64.2	738	AT+URI : Resource parameters
4.2	739
	740
64.2	741	(% style="color:#037691" %)UDP Management
4.2	742
64.2	743	AT+CFM : Upload confirmation mode (only valid for UDP)
4.2	744
	745
64.2	746	(% style="color:#037691" %)MQTT Management
4.2	747
64.2	748	AT+CLIENT : Get or Set MQTT client
4.2	749
64.2	750	AT+UNAME : Get or Set MQTT Username
4.2	751
64.2	752	AT+PWD : Get or Set MQTT password
4.2	753
64.2	754	AT+PUBTOPIC : Get or Set MQTT publish topic
4.2	755
64.2	756	AT+SUBTOPIC : Get or Set MQTT subscription topic
4.2	757
	758
64.2	759	(% style="color:#037691" %)Information
4.2	760
64.2	761	AT+FDR : Factory Data Reset
4.2	762
64.2	763	AT+PWORD : Serial Access Password
4.2	764
	765
	766
64.4	767	= 5. FAQ =
4.2	768
64.4	769	== 5.1 How to Upgrade Firmware ==
6.3	770
4.2	771
31.35	772	(((
64.4	773	User can upgrade the firmware for 1) bug fix, 2) new feature release.
31.35	774	)))
4.2	775
31.35	776	(((
64.4	777	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>>http://wiki.dragino.com/xwiki/bin/view/Main/Firmware%20Upgrade%20Instruction%20for%20STM32%20base%20products/#H2.HardwareUpgradeMethodSupportList]]
31.35	778	)))
4.2	779
31.35	780	(((
64.5	781	(% style="color:red" %)Notice, NSE01 and LSE01 share the same mother board. They use the same connection and method to update.
31.35	782	)))
4.2	783
	784
	785
65.23	786	== 5.2 Can I calibrate NSE01 to different soil types? ==
	787
	788	(((
	789	NSE01 is calibrated for saline-alkali soil and loamy soil. If users want to use it for other soil, they can calibrate the value in the IoT platform base on the value measured by saline-alkali soil and loamy soil. The formula can be found at [[this link>>https://www.dragino.com/downloads/downloads/LoRa_End_Node/LSE01/Calibrate_to_other_Soil_20220605.pdf]].
	790	)))
	791
	792
64.5	793	= 6. Trouble Shooting =
4.2	794
64.5	795	== 6.1 Connection problem when uploading firmware ==
4.9	796
4.2	797
65.20	798	(((
	799	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]]
	800	)))
	801
64.5	802	(% class="wikigeneratedid" %)
31.29	803	(((
65.20	804
31.29	805	)))
4.2	806
	807
64.5	808	== 6.2 AT Command input doesn't work ==
4.2	809
31.30	810	(((
64.5	811	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.
65.22	812
65.23	813
31.30	814	)))
4.2	815
	816
64.5	817	= 7. Order Info =
4.2	818
	819
64.5	820	Part Number: (% style="color:#4f81bd" %)NSE01
4.7	821
4.2	822
31.10	823	(% class="wikigeneratedid" %)
	824	(((
	825
	826	)))
	827
65.2	828	= 8. Packing Info =
4.2	829
4.3	830	(((
31.39	831
	832
31.40	833	(% style="color:#037691" %)Package Includes:
64.5	834
65.1	835	* NSE01 NB-IoT Soil Moisture & EC Sensor x 1
64.5	836	* External antenna x 1
4.3	837	)))
4.2	838
4.3	839	(((
31.40	840
	841
	842	(% style="color:#037691" %)Dimension and weight:
4.2	843
64.5	844	* Size: 195 x 125 x 55 mm
	845	* Weight: 420g
4.3	846	)))
31.11	847
64.5	848	(((
31.11	849
64.5	850
	851
	852
4.3	853	)))
4.2	854
64.5	855	= 9. Support =
4.2	856
	857	* 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.
	858	* 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]]

Wiki source code of NDDS75 NB-IoT Distance Detect Sensor User Manual

Applications