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

Version 97.2 by Xiaoling on 2022/07/09 11:09

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