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

Version 97.22 by Xiaoling on 2022/07/11 14:08

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