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

Version 100.3 by Xiaoling on 2022/08/08 16:07

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