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

Version 97.9 by Xiaoling on 2022/07/09 11:30

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