Changes for page NDDS75 -- NB-IoT Distance Detect Sensor User Manual

Last modified by Bei Jinggeng on 2024/05/31 09:53

From 102.1 to 101.1 From 109.1 to 108.27

From version 108.27

edited by Xiaoling
on 2024/01/19 17:55

Change comment: There is no comment for this version

To version 102.1

edited by David Huang
on 2022/09/08 17:53

Change comment: Uploaded new attachment "image-20220908175333-2.png", version {1}

Raw
Rendered

Summary

Page properties (3 modified, 0 added, 0 removed)
Attachments (0 modified, 0 added, 1 removed)
- image-20221009001114-1.png

Details

Page properties

Title

@@ -1,1 +1,1 @@
--NDDS75 -- NB-IoT Distance Detect Sensor User Manual
++NDDS75 NB-IoT Distance Detect Sensor User Manual

Author

@@ -1,1 +1,1 @@
--XWiki.Xiaoling
++XWiki.David

Content

@@ -1,5 +3,3 @@
--
--
  (% style="text-align:center" %)
  [[image:image-20220709085040-1.png||height="542" width="524"]]
@@ -18,6 +18,7 @@
  = 1.  Introduction =
++
  == 1.1  What is NDDS75 Distance Detection Sensor ==
  (((
@@ -55,6 +55,7 @@
  [[image:1657327959271-447.png]]
++
  == 1.2  Features ==
@@ -71,6 +71,9 @@
  * Micro SIM card slot for NB-IoT SIM
  * 8500mAh Battery for long term use
++
++
++
  == 1.3  Specification ==
@@ -79,15 +79,19 @@
  * Supply Voltage: 2.1v ~~ 3.6v
  * Operating Temperature: -40 ~~ 85°C
++
++
  (% style="color:#037691" %)**NB-IoT Spec:**
--* B1 @H-FDD: 2100MHz
--* B3 @H-FDD: 1800MHz
--* B8 @H-FDD: 900MHz
--* B5 @H-FDD: 850MHz
--* B20 @H-FDD: 800MHz
--* B28 @H-FDD: 700MHz
++* - B1 @H-FDD: 2100MHz
++* - B3 @H-FDD: 1800MHz
++* - B8 @H-FDD: 900MHz
++* - B5 @H-FDD: 850MHz
++* - B20 @H-FDD: 800MHz
++* - B28 @H-FDD: 700MHz
++
++
  (% style="color:#037691" %)**Battery:**
  * Li/SOCI2 un-chargeable battery
@@ -96,11 +96,16 @@
  * Max continuously current: 130mA
  * Max boost current: 2A, 1 second
++
++
  (% style="color:#037691" %)**Power Consumption**
  * STOP Mode: 10uA @ 3.3v
  * Max transmit power: 350mA@3.3v
++
++
++
  == 1.4  Applications ==
@@ -115,6 +115,8 @@
++
++
  == 1.5  Pin Definitions ==
@@ -121,8 +121,10 @@
  [[image:1657328609906-564.png]]
++
  = 2.  Use NDDS75 to communicate with IoT Server =
++
  == 2.1  How it works ==
@@ -145,8 +145,10 @@
  )))
++
  == 2.2  Configure the NDDS75 ==
++
  === 2.2.1  Test Requirement ===
@@ -158,6 +158,8 @@
  * The local NB-IoT network used the band that NDDS75 supports.
  * Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
++
++
  (((
  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.
  )))
@@ -166,6 +166,7 @@
  [[image:1657328756309-230.png]]
++
  === 2.2.2  Insert SIM card ===
@@ -177,9 +177,11 @@
  User need to take out the NB-IoT module and insert the SIM card like below:
  )))
++
  [[image:1657328884227-504.png]]
++
  === 2.2.3  Connect USB – TTL to NDDS75 to configure it ===
@@ -192,13 +192,13 @@
  [[image:image-20220709092052-2.png]]
--(% style="color:blue" %)**Connection:**
++**Connection:**
-- (% style="background-color:yellow" %)**USB TTL GND <~-~-~-~-> GND**
++ (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND
--**~ (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD(%%)**
++ (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD
--**~ (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD(%%)**
++ (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD
  In the PC, use below serial tool settings:
@@ -221,6 +221,7 @@
  )))
++
  === 2.2.4  Use CoAP protocol to uplink data ===
@@ -235,23 +235,23 @@
  (% style="color:blue" %)**AT+PRO=1**  (%%)                                             ~/~/ Set to use CoAP protocol to uplink
  )))
  * (((
--(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   **  (%%)~/~/  to set CoAP server address and port
++(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   **  (%%)~/~/ to set CoAP server address and port
  )))
  * (((
--(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%)      ~/~/  Set COAP resource path
++(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%)      ~/~/Set COAP resource path
++
  )))
  (((
  For parameter description, please refer to AT command set
--
--
  )))
  [[image:1657330452568-615.png]]
++
  (((
  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.
  )))
@@ -259,13 +259,16 @@
  [[image:1657330472797-498.png]]
++
  === 2.2.5  Use UDP protocol to uplink data(Default protocol) ===
--* (% style="color:blue" %)**AT+PRO=2   ** (%%)        ~/~/  Set to use UDP protocol to uplink
--* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601   **  (%%) ~/~/  to set UDP server address and port
--* (% style="color:blue" %)**AT+CFM=1       **   (%%) ~/~/  If the server does not respond, this command is unnecessary
++* (% style="color:blue" %)**AT+PRO=2   ** (%%)        ~/~/ Set to use UDP protocol to uplink
++* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601   **  (%%) ~/~/ to set UDP server address and port
++* (% style="color:blue" %)**AT+CFM=1       **   (%%) ~/~/ If the server does not respond, this command is unnecessary
++
++
  [[image:1657330501006-241.png]]
@@ -272,17 +272,20 @@
  [[image:1657330533775-472.png]]
++
  === 2.2.6  Use MQTT protocol to uplink data ===
--* (% style="color:blue" %)**AT+PRO=3   **       (%%)                                        ~/~/  Set to use MQTT protocol to uplink
--* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   **   (%%)    ~/~/  Set MQTT server address and port
--* (% style="color:blue" %)**AT+CLIENT=CLIENT       **                            (%%)~/~/  Set up the CLIENT of MQTT
--* (% style="color:blue" %)**AT+UNAME=UNAME                                **(%%)~/~/  Set the username of MQTT
--* (% style="color:blue" %)**AT+PWD=PWD                                         **(%%)~/~/  Set the password of MQTT
--* (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB                 **(%%)~/~/   Set the sending topic of MQTT
--* (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB          **(%%)       ~/~/   Set the subscription topic of MQTT
++* (% style="color:blue" %)**AT+PRO=3   **       (%%)                                        ~/~/Set to use MQTT protocol to uplink
++* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   **   (%%)    ~/~/Set MQTT server address and port
++* (% style="color:blue" %)**AT+CLIENT=CLIENT       **                            (%%)~/~/Set up the CLIENT of MQTT
++* (% style="color:blue" %)**AT+UNAME=UNAME                                **(%%)~/~/Set the username of MQTT
++* (% style="color:blue" %)**AT+PWD=PWD                                         **(%%)~/~/Set the password of MQTT
++* (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB                 **(%%)~/~/Set the sending topic of MQTT
++* (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB          **(%%)       ~/~/Set the subscription topic of MQTT
++
++
  [[image:1657249978444-674.png]]
@@ -294,12 +294,15 @@
  )))
++
  === 2.2.7  Use TCP protocol to uplink data ===
--* (% style="color:blue" %)**AT+PRO=4   ** (%%)                                          ~/~/  Set to use TCP protocol to uplink
--* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600   **(%%) ~/~/    to set TCP server address and port
++* (% style="color:blue" %)**AT+PRO=4   ** (%%)                                          ~/~/ Set to use TCP protocol to uplink
++* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600   **(%%) ~/~/ to set TCP server address and port
++
++
  [[image:image-20220709093918-1.png]]
@@ -306,41 +306,36 @@
  [[image:image-20220709093918-2.png]]
++
  === 2.2.8  Change Update Interval ===
  User can use below command to change the (% style="color:green" %)**uplink interval**.
--* (% style="color:blue" %)**AT+TDC=600      **  (%%)~/~/  Set Update Interval to 600s
++* (% style="color:blue" %)**AT+TDC=600      **  (%%)~/~/ Set Update Interval to 600s
--(((
--
--(% style="color:red" %)**NOTE:**
--(% style="color:red" %)**1. By default, the device will send an uplink message every 1 hour.**
--
--(% style="color:red" %)**2. When the firmware version is v1.3.2 and later firmware:**
++(((
++(% style="color:red" %)**NOTE: By default, the device will send an uplink message every 1 hour.**
  )))
--(% style="color:red" %)**By default, the device will send an uplink message every 2 hours. Each Uplink Include 8 set of records in this 2 hour (15 minute interval / record).**
  == 2.3  Uplink Payload ==
--=== 2.3.1  Before Firmware v1.3.2 ===
--
  In this mode, uplink payload includes in total 14 bytes
--(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:440px" %)
--|=(% style="width: 61px;background-color:#4F81BD;color:white" %)(((
++
++(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %)
++|=(% style="width: 60px;" %)(((
  **Size(bytes)**
--)))|=(% style="width: 61px;background-color:#4F81BD;color:white" %)**6**|=(% style="width: 37px;background-color:#4F81BD;color:white" %)2|=(% style="width: 37px;background-color:#4F81BD;color:white" %)**2**|=(% style="width: 82px;background-color:#4F81BD;color:white" %)**1**|=(% style="width: 102px;background-color:#4F81BD;color:white" %)**2**|=(% style="width: 60px;background-color:#4F81BD;color:white" %)**1**
--|(% 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"]]
++)))|=(% style="width: 60px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 80px;" %)**1**|=(% style="width: 100px;" %)**2**|=(% style="width: 60px;" %)**1**
++|(% 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"]]
  (((
--If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS75 uplink data.
++If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS751 uplink data.
  )))
@@ -347,68 +347,41 @@
  [[image:1657331036973-987.png]]
--The payload is **ASCII** string, representative same HEX:
--
--(% style="background-color:yellow" %)**0x 724031556159 0064 0c6c 19 0292 00 **
--
--**where :**
--
--* (% style="color:#037691" %)**Device ID:**(%%) 0x724031556159 = 724031556159
--
--* (% style="color:#037691" %)**Version:**(%%)    0x0064=100=1.0.0
--
--* (% style="color:#037691" %)**BAT:** (%%)      0x0c6c = 3180 mV = 3.180V
--
--* (% style="color:#037691" %)**Signal:**(%%)   0x19 = 25
--
--* (% style="color:#037691" %)**Distance:**  (%%)0x0292= 658 mm
--
--* (% style="color:#037691" %)**Interrupt:**(%%) 0x00 = 0
--
--=== 2.3.2  Since firmware v1.3.2 ===
--
--
--In this mode, uplink payload includes 69 bytes in total by default.
--
--Each time the device uploads a data package, 8 sets of recorded data will be attached. Up to 32 sets of recorded data can be uploaded.
--
--(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:490px" %)
--|(% style="background-color:#4f81bd; color:white; width:60px" %)**Size(bytes)**|(% style="background-color:#4f81bd; color:white; width:40px" %)**8**|(% style="background-color:#4f81bd; color:white; width:25px" %)**2**|(% style="background-color:#4f81bd; color:white; width:25px" %)**2**|(% style="background-color:#4f81bd; color:white; width:60px" %)**1**|(% style="background-color:#4f81bd; color:white; width:25px" %)**1**|(% style="background-color:#4f81bd; color:white; width:40px" %)**1**|(% style="background-color:#4f81bd; color:white; width:40px" %)**2**|(% style="background-color:#4f81bd; color:white; width:70px" %)**4**|(% style="background-color:#4f81bd; color:white; width:40px" %)**2**|(% style="background-color:#4f81bd; color:white; width:65px" %)**4**
--|(% style="width:95px" %)Value|(% style="width:84px" %)Device ID|(% style="width:44px" %)Ver|(% style="width:48px" %)BAT|(% style="width:123px" %)Signal Strength|(% style="width:55px" %)MOD|(% style="width:80px" %)Interrupt|(% style="width:77px" %)Distance|(% style="width:94px" %)Timestamp|(% style="width:77px" %)Distance|(% style="width:116px" %)Timestamp.......
--
--If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS75 uplink data.
--
--[[image:image-20220908175246-1.png]]
--
--
++(((
  The payload is ASCII string, representative same HEX:
++)))
--**0x (% style="color:red" %)f867787050213317 (% style="color:blue" %)0084 (% style="color:green" %)0cf4 (% style="color:#00b0f0" %)1e (% style="color:#7030a0" %)01 (% style="color:#d60093" %)00(% style="color:#a14d07" %) 0039 (% style="color:#0020b0" %)6315537b (% style="color:#663300" %)00396319baf0 00396319ba3c 00396319b988 00396319b8d4 00396319b820 00396319b76c 00396319b6b8 00396319b604 (%%)**
++(((
++0x72403155615900640c6c19029200 where:
++)))
--**where:**
++* (((
++Device ID: 0x724031556159 = 724031556159
++)))
++* (((
++Version: 0x0064=100=1.0.0
++)))
--* (% style="color:#037691" %)**Device ID:**(%%) f867787050213317 = f867787050213317
++* (((
++BAT: 0x0c6c = 3180 mV = 3.180V
++)))
++* (((
++Signal: 0x19 = 25
++)))
++* (((
++Distance: 0x0292= 658 mm
++)))
++* (((
++Interrupt: 0x00 = 0
--* (% style="color:#037691" %)**Version:**(%%) 0x0084=132=1.3.2
--* (% style="color:#037691" %)**BAT:**(%%)       0x0cf4 = 3316 mV = 3.316V
--* (% style="color:#037691" %)**Singal:**(%%)   0x1e = 30
++
++)))
--* (% style="color:#037691" %)**Mod:**(%%)**     **0x01 = 1
--
--* (% style="color:#037691" %)**Interrupt:**(%%) 0x00= 0
--
--* (% style="color:#037691" %)**Distance:**(%%) 0x0039= 57 = 57
--
--* (% style="color:#037691" %)**Time stamp:**(%%) 0x6315537b =1662342011  ([[Unix Epoch Time>>url:http://www.epochconverter.com/]])
--
--* (% style="color:#037691" %)**Distance,Time stamp:**(%%) 00396319baf0
--
--* (% style="color:#037691" %)**8 sets of recorded data: Distance,Time stamp :**(%%) //**00396319ba3c**//,.......
--
  == 2.4  Payload Explanation and Sensor Interface ==
++
  === 2.4.1  Device ID ===
@@ -423,7 +423,7 @@
  )))
  (((
--(% style="color:blue" %)**Example :**
++**Example:**
  )))
  (((
@@ -431,22 +431,11 @@
  )))
  (((
--The Device ID is stored in a none-erase area, Upgrade the firmware or run (% style="color:blue" %)**AT+FDR**(%%) won't erase Device ID.
++The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID.
  )))
--(% style="color:red" %)**NOTE: When the firmware version is v1.3.2 and later firmware:**
--(% style="color:red" %)**By default, the Device ID equal to the last 15 bits of IMEI.**
--
--User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
--
--
--(% style="color:blue" %)**Example :**
--
--AT+DEUI=868411056754138
--
--
  === 2.4.2  Version Info ===
@@ -459,6 +459,7 @@
  )))
++
  === 2.4.3  Battery Info ===
@@ -471,6 +471,7 @@
  )))
++
  === 2.4.4  Signal Strength ===
@@ -503,6 +503,7 @@
  )))
++
  === 2.4.5  Distance ===
@@ -509,13 +509,23 @@
  Get the distance. Flat object range 280mm - 7500mm.
  (((
--For example, if the data you get from the register is **__0x0B 0x05__**, the distance between the sensor and the measured object is(% style="color:blue" %)** 0B05(H) = 2821(D) = 2821mm.**
++For example, if the data you get from the register is **__0x0B 0x05__**, the distance between the sensor and the measured object is
  )))
  (((
++(((
++(% style="color:blue" %)**                                                        0B05(H) = 2821(D) = 2821mm.**
++)))
++)))
++
++(((
  )))
++(((
++
++)))
++
  === 2.4.6  Digital Interrupt ===
@@ -528,7 +528,7 @@
  )))
  (((
--(% 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]])**.**
++(% 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]])**.**
  )))
@@ -536,8 +536,9 @@
  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.
  )))
++
  (((
--**Example:**
++Example:
  )))
  (((
@@ -549,6 +549,7 @@
  )))
++
  === 2.4.7  +5V Output ===
@@ -556,12 +556,17 @@
  NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling.
  )))
++
  (((
  The 5V output time can be controlled by AT Command.
++
++
  )))
  (((
  (% style="color:blue" %)**AT+5VT=1000**
++
++
  )))
  (((
@@ -569,17 +569,15 @@
  )))
++
  == 2.5  Downlink Payload ==
  By default, NDDS75 prints the downlink payload to console port.
--(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:515px" %)
--|(% style="background-color:#4f81bd; color:white; width:208px" %)**Downlink Control Type**|(% style="background-color:#4f81bd; color:white; width:56px" %)**FPort**|(% style="background-color:#4f81bd; color:white; width:100px" %)**Type Code**|(% style="background-color:#4f81bd; color:white; width:151px" %)**Downlink payload size(bytes)**
--|(% style="width:208px" %)TDC (Transmit Time Interval)|(% style="width:56px" %)Any|(% style="width:100px" %)01|(% style="width:154px" %)4
--|(% style="width:208px" %)RESET|(% style="width:56px" %)Any|(% style="width:100px" %)04|(% style="width:154px" %)2
--|(% style="width:208px" %)INTMOD|(% style="width:56px" %)Any|(% style="width:100px" %)06|(% style="width:154px" %)4
++[[image:image-20220709100028-1.png]]
++
  (((
  (% style="color:blue" %)**Examples:**
  )))
@@ -624,85 +624,126 @@
  )))
--== 2.6  Distance alarm function(Since firmware v1.3.2) ==
++== 2.6  LED Indicator ==
--(% style="color:blue" %)** ➢ AT Command:**
--(% style="color:#037691" %)** AT+ LDDSALARM=min,max**
++The NDDS75 has an internal LED which is to show the status of different state.
--² When min=0, and max≠0, Alarm higher than max
--² When min≠0, and max=0, Alarm lower than min
++* 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)
++* Then the LED will be on for 1 second means device is boot normally.
++* After NDDS75 join NB-IoT network. The LED will be ON for 3 seconds.
++* For each uplink probe, LED will be on for 500ms.
--² When min≠0 and max≠0, Alarm higher than max or lower than min
++(((
++
++)))
--(% style="color:blue" %)** Example:**
--**AT+ LDDSALARM=260,2000**    ~/~/ Alarm when distance lower than 260.
++== 2.7  Firmware Change Log ==
--== 2.7  Set the number of data to be uploaded and the recording time ==
++(((
++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]]
++)))
++(((
++
++)))
--(% style="color:blue" %)** ➢ AT Command:**
++(((
++Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
++)))
--* (% style="color:#037691" %)** AT+TR=900** (%%)                ~/~/ The unit is seconds, and the default is to record data once every 900 seconds.( The minimum can be set to 180 seconds)
--* (% style="color:#037691" %)** AT+NOUD=8**             (%%) ~/~/  The device uploads 8 sets of recorded data by default. Up to 32 sets of record data can be uploaded.
-- The diagram below explains the relationship between TR, NOUD, and TDC more clearly**:**
--[[image:image-20221009001114-1.png||height="687" width="955"]]
++== 2.8  Battery Analysis ==
--== 2.8  Read or Clear cached data ==
++=== 2.8.1  Battery Type ===
--(% style="color:blue" %)** ➢ AT Command:**
++(((
++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.
++)))
--* (% style="color:#037691" %)** AT+CDP **  (%%)           ~/~/  Read cached data
--* (% style="color:#037691" %)** AT+CDP=0**  (%%)       ~/~/  Clear cached data
++(((
++The battery is designed to last for several years depends on the actually use environment and update interval.
++)))
--[[image:image-20220908175333-2.png]]
++(((
++The battery related documents as below:
++)))
++* [[Battery Dimension>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
++* [[Lithium-Thionyl Chloride Battery datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
++* [[Lithium-ion Battery-Capacitor datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
--== 2.9  LED Indicator ==
++(((
++[[image:image-20220709101450-2.png]]
++)))
--The NDDS75 has an internal LED which is to show the status of different state.
++=== 2.8.2  Power consumption Analyze ===
--* 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)
--* Then the LED will be on for 1 second means device is boot normally.
--* After NDDS75 join NB-IoT network. The LED will be ON for 3 seconds.
--* For each uplink probe, LED will be on for 500ms.
  (((
--
++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.
  )))
--== 2.10  Firmware Change Log ==
++(((
++Instruction to use as below:
++)))
++(((
++(% 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/]]
++)))
++
  (((
--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]]
++(% style="color:blue" %)**Step 2: **(%%) Open it and choose
  )))
++* (((
++Product Model
++)))
++* (((
++Uplink Interval
++)))
++* (((
++Working Mode
++)))
++
  (((
--Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
++And the Life expectation in difference case will be shown on the right.
  )))
++[[image:image-20220709110451-3.png]]
--== 2.11  Battery & Power Consumption ==
--NDDS75 uses ER26500 + SPC1520 battery pack. See below link for detail information about the battery info and how to replace.
++=== 2.8.3  Battery Note ===
--[[**Battery Info & Power Consumption Analyze**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20calculate%20the%20battery%20life%20of%20Dragino%20sensors%3F/]] .
++(((
++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.
++)))
++
++
++=== 2.8.4  Replace the battery ===
++
++
++(((
++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).
++)))
++
++
++
  = 3.  Access NB-IoT Module =
@@ -719,8 +719,10 @@
  [[image:1657333200519-600.png]]
++
  = 4.  Using the AT Commands =
++
  == 4.1  Access AT Commands ==
@@ -727,94 +727,80 @@
  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]]
--AT+<CMD>?                    :   Help on <CMD>
++AT+<CMD>?                    : Help on <CMD>
--AT+<CMD>                      :   Run <CMD>
++AT+<CMD>                      : Run <CMD>
--AT+<CMD>=<value>      :   Set the value
++AT+<CMD>=<value>      : Set the value
--AT+<CMD>=?                  :   Get the value
++AT+<CMD>=?                  : Get the value
  (% style="color:#037691" %)**General Commands**(%%)
--AT                            :   Attention
++AT                            : Attention
--AT?                           :  Short Help
++AT?                           : Short Help
--ATZ                          :   MCU Reset
++ATZ                          : MCU Reset
--AT+TDC                   :   Application Data Transmission Interval
++AT+TDC                   : Application Data Transmission Interval
--AT+CFG                   :   Print all configurations
++AT+CFG                   : Print all configurations
--AT+CFGMOD           :   Working mode selection
++AT+CFGMOD           : Working mode selection
--AT+INTMOD            :   Set the trigger interrupt mode
++AT+INTMOD            : Set the trigger interrupt mode
--AT+5VT                     :  Set extend the time of 5V power
++AT+5VT                     : Set extend the time of 5V power
--AT+PRO                    :   Choose agreement
++AT+PRO                    : Choose agreement
--AT+WEIGRE              :   Get weight or set weight to 0
++AT+WEIGRE              : Get weight or set weight to 0
--AT+WEIGAP              :   Get or Set the GapValue of weight
++AT+WEIGAP              : Get or Set the GapValue of weight
--AT+RXDL                   :   Extend the sending and receiving time
++AT+RXDL                   : Extend the sending and receiving time
--AT+CNTFAC              :   Get or set counting parameters
++AT+CNTFAC              : Get or set counting parameters
--AT+SERVADDR         :   Server Address
++AT+SERVADDR          : Server Address
--AT+TR               :  Get or Set record time"
--AT+APN            :  Get or set the APN
--
--AT+FBAND       :  Get or Set whether to automatically modify the frequency band
--
--AT+DNSCFG     :  Get or Set DNS Server
--
--AT+GETSENSORVALUE   :   Returns the current sensor measurement
--
--AT+NOUD  :     Get or Set the number of data to be uploaded
--
--AT+CDP     :      Read or Clear cached data
--
--AT+LDDSALARM :   Get or Set alarm of distance
--
--
  (% style="color:#037691" %)**COAP Management**
--AT+URI            :   Resource parameters
++AT+URI            : Resource parameters
  (% style="color:#037691" %)**UDP Management**
--AT+CFM          :   Upload confirmation mode (only valid for UDP)
++AT+CFM          : Upload confirmation mode (only valid for UDP)
  (% style="color:#037691" %)**MQTT Management**
--AT+CLIENT         :   Get or Set MQTT client
++AT+CLIENT               : Get or Set MQTT client
--AT+UNAME        :   Get or Set MQTT Username
++AT+UNAME             : Get or Set MQTT Username
--AT+PWD             :   Get or Set MQTT password
++AT+PWD                  : Get or Set MQTT password
--AT+PUBTOPIC     :   Get or Set MQTT publish topic
++AT+PUBTOPIC          : Get or Set MQTT publish topic
--AT+SUBTOPIC     :   Get or Set MQTT subscription topic
++AT+SUBTOPIC          : Get or Set MQTT subscription topic
  (% style="color:#037691" %)**Information**
--AT+FDR              :   Factory Data Reset
++AT+FDR              : Factory Data Reset
--AT+PWORD       :   Serial Access Password
++AT+PWORD       : Serial Access Password
++
  = 5.  FAQ =
++
  == 5.1  How to Upgrade Firmware ==
@@ -831,8 +831,10 @@
  )))
++
  = 6.  Trouble Shooting =
++
  == 6.1  Connection problem when uploading firmware ==
@@ -845,20 +845,17 @@
  )))
++
  == 6.2  AT Command input doesn't work ==
  (((
  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.
++
++
  )))
--== 6.3  Not able to connect to NB-IoT network and keep showing "Signal Strength:99". ==
--
--
--This means sensor is trying to join the NB-IoT network but fail. Please see this link for **//[[trouble shooting for signal strenght:99>>doc:Main.CSQ\:99,99.WebHome]]//**.
--
--
  = 7.  Order Info =
@@ -865,6 +865,11 @@
  Part Number**:** (% style="color:#4f81bd" %)**NSDDS75**
++(% class="wikigeneratedid" %)
++(((
++
++)))
++
  = 8.  Packing Info =
  (((
@@ -879,6 +879,7 @@
  (((
++
  (% style="color:#037691" %)**Dimension and weight**:
  * Device Size: 13.0 x 5 x 4.5 cm
@@ -890,6 +890,7 @@
  (((
++
  )))
@@ -897,5 +897,6 @@
  * 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.
--
  * 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]]
++
++

image-20221009001114-1.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Edwin

Size

...	...	@@ -1,1 +1,0 @@
1		-282.9 KB

Content