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

Version 97.18 by Xiaoling on 2022/07/09 11:54

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