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

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

From version < 103.1 >

edited by David Huang
on 2022/09/08 18:02

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 (1 modified, 0 added, 0 removed)

Details

Page properties

Content

@@ -72,6 +72,8 @@
  * 8500mAh Battery for long term use
++
++
  == 1.3  Specification ==
@@ -80,6 +80,8 @@
  * Supply Voltage: 2.1v ~~ 3.6v
  * Operating Temperature: -40 ~~ 85°C
++
++
  (% style="color:#037691" %)**NB-IoT Spec:**
  * - B1 @H-FDD: 2100MHz
@@ -89,6 +89,8 @@
  * - B20 @H-FDD: 800MHz
  * - B28 @H-FDD: 700MHz
++
++
  (% style="color:#037691" %)**Battery:**
  * Li/SOCI2 un-chargeable battery
@@ -97,6 +97,8 @@
  * Max continuously current: 130mA
  * Max boost current: 2A, 1 second
++
++
  (% style="color:#037691" %)**Power Consumption**
  * STOP Mode: 10uA @ 3.3v
@@ -103,6 +103,8 @@
  * Max transmit power: 350mA@3.3v
++
++
  == 1.4  Applications ==
@@ -166,6 +166,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.
  )))
@@ -279,6 +279,8 @@
  * (% 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]]
@@ -297,6 +297,8 @@
  * (% 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]]
@@ -315,6 +315,8 @@
  * (% 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]]
@@ -329,17 +329,14 @@
  * (% style="color:blue" %)**AT+TDC=600      **  (%%)~/~/ Set Update Interval to 600s
++
++
  (((
  (% style="color:red" %)**NOTE: By default, the device will send an uplink message every 1 hour.**
--
--
  )))
--**NOTE:When the firmware version is v1.3.2 and later firmware:**
--**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 ==
@@ -387,37 +387,11 @@
  * (((
  Interrupt: 0x00 = 0
++
++
  )))
--**NOTE:When the firmware version is v1.3.2 and later firmware:**
--
--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.
--
--|**Size(bytes)**|**8**|2|2|1|1|1|2|4|2|4
--|**Value**|Device ID|Ver|BAT|Signal Strength|MOD|Interrupt|Distance|Timestamp|Distance|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:red" %)1e(% style="color:blue" %)01(% style="color:green" %)00(% style="color:red" %)**//00396319bb32//**00396319baf0//**00396319ba3c**//00396319b988//**00396319b8d4**//00396319b820//**00396319b76c**//00396319b6b8//**00396319b604**//(%%) where:
--
--* (% style="color:green" %)Device ID: f867787050213317 = f867787050213317
--* (% style="color:red" %)Version: 0x0084=132=1.3.2
--* (% style="color:green" %)BAT: 0x0cf4 = 3316 mV = 3.316V
--* (% style="color:blue" %)Singal: 0x1e = 30
--* (% style="color:red" %)Mod: 0x01 = 1
--* Interrupt: 0x00= 0
--* Distance: 0x0039= 57 = 57
--* Time stamp : 0x6315537b =1662342011  ([[Unix Epoch Time>>url:http://www.epochconverter.com/]])
--* Distance,Time stamp : 00396319baf0
--* (% style="color:red" %) 8 sets of recorded data: Distance,Time stamp : //**00396319ba3c**//,.......
--
  == 2.4  Payload Explanation and Sensor Interface ==
@@ -447,16 +447,7 @@
  )))
--**NOTE:When the firmware version is v1.3.2 and later firmware:**
--By default, the Device ID equal to the last 15 bits of IMEI.
--
--User can use **AT+DEUI** to set Device ID
--
--**Example:**
--
--AT+DEUI=868411056754138
--
  === 2.4.2  Version Info ===
@@ -652,44 +652,10 @@
  )))
--== 2.6 Distance alarm function ==
--➢ AT Command:
++== 2.6  LED Indicator ==
--AT+ LDDSALARM=min,max
--² When min=0, and max≠0, Alarm higher than max
--
--² When min≠0, and max=0, Alarm lower than min
--
--² When min≠0 and max≠0, Alarm higher than max or lower than min
--
--Example:
--
--AT+ LDDSALARM=260,2000 ~/~/ Alarm when distance lower than 260.
--
--
--== 2.7 Set the number of data to be uploaded and the recording time ==
--
--➢ AT Command:
--
--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)
--
--AT+NOUD=8  ~/~/The device uploads 8 sets of recorded data by default. Up to 32 sets of record data can be uploaded.
--
--== 2.8 Read or Clear cached data ==
--
--➢ AT Command:
--
--AT+CDP    ~/~/ Read cached data
--
--[[image:image-20220908175333-2.png]]
--
--AT+CDP=0    ~/~/ Clear cached data
--
--== 2.9  LED Indicator ==
--
--
  The NDDS75 has an internal LED which is to show the status of different state.
@@ -704,7 +704,7 @@
--== 2.10  Firmware Change Log ==
++== 2.7  Firmware Change Log ==
  (((
@@ -721,10 +721,10 @@
--== 2.11  Battery Analysis ==
++== 2.8  Battery Analysis ==
--=== 2.11.1  Battery Type ===
++=== 2.8.1  Battery Type ===
  (((
@@ -749,7 +749,7 @@
--=== 2.11.2  Power consumption Analyze ===
++=== 2.8.2  Power consumption Analyze ===
  (((
@@ -788,7 +788,7 @@
--=== 2.11.3  Battery Note ===
++=== 2.8.3  Battery Note ===
  (((
@@ -797,7 +797,7 @@
--=== 2.11.4  Replace the battery ===
++=== 2.8.4  Replace the battery ===
  (((
@@ -871,23 +871,7 @@
  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
@@ -1011,3 +1011,5 @@
  * 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]]
++
++

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

Summary

Details

Applications

Navigation