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

Version 97.3 by Xiaoling on 2022/07/09 11:10

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