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

Version 100.4 by Xiaoling on 2022/08/22 14:38

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

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

Applications