Wiki source code of DS03A-NB -- NB-IoT Door Sensor User Manual
Version 132.2 by Mengting Qiu on 2023/11/15 17:14
Show last authors
| author | version | line-number | content |
|---|---|---|---|
| 1 | (% style="text-align:center" %) | ||
| 2 | [[image:image-20231011093014-5.png]] | ||
| 3 | |||
| 4 | |||
| 5 | |||
| 6 | |||
| 7 | **Table of Contents:** | ||
| 8 | |||
| 9 | {{toc/}} | ||
| 10 | |||
| 11 | |||
| 12 | |||
| 13 | |||
| 14 | |||
| 15 | |||
| 16 | = 1. Introduction = | ||
| 17 | |||
| 18 | == 1.1 What is DS03A-NB NB-IoT Door Sensor == | ||
| 19 | |||
| 20 | |||
| 21 | The Dragino DS03A-NB is a (% style="color:blue" %) **NB-IoT Door Sensor**(%%) for Internet of Things solution. It (% style="color:blue" %)**detects door open/close status**(%%) and uplinks to IoT server via NB-IoT network. user can see the door status, open duration, open counts in the IoT Server. | ||
| 22 | |||
| 23 | The DS03A-NB will send periodically data every 2 hours as well as for each door open/close action. It also counts the door open times and calculates the last door open duration. Users can also disable the uplink for each open/close event, instead, DS03A-NB can count each open event and uplink periodically. | ||
| 24 | |||
| 25 | DS03A-NB supports (% style="color:blue" %)**Datalog Feature,** (%%)it can save the data when there is no NB-IoT network and uplink when network recover. | ||
| 26 | |||
| 27 | DS03A-NB has the (% style="color:blue" %)**Open Alarm Feature**,(%%) user can set this feature so the device will send an alarm if the door has been open for a certain time. | ||
| 28 | |||
| 29 | DS03A-NB is designed for outdoor use. It has a weatherproof enclosure and industrial level battery to work in low to high temperatures | ||
| 30 | |||
| 31 | DS03A-NB supports different uplink methods including (% style="color:blue" %)**MQTT, MQTTs, UDP & TCP**(%%) for different application requirement, and support uplinks to various IoT Servers. | ||
| 32 | |||
| 33 | DS03A-NB (% style="color:blue" %)**supports BLE configure **(%%)and(% style="color:blue" %)** OTA update**(%%) which make user easy to use. | ||
| 34 | |||
| 35 | DS03A-NB is powered by (% style="color:blue" %)**8500mAh Li-SOCI2 battery**(%%), it is designed for long-term use up to several years. | ||
| 36 | |||
| 37 | DS03A-NB has optional built-in SIM card and default IoT server connection version. Which makes it works with simple configuration. | ||
| 38 | |||
| 39 | [[image:image-20231011093807-6.png||height="278" width="879"]] | ||
| 40 | |||
| 41 | |||
| 42 | == 1.2 Features == | ||
| 43 | |||
| 44 | |||
| 45 | * NB-IoT Bands: B1/B2/B3/B4/B5/B8/B12/B13/B17/B18/B19/B20/B25/B28/B66/B70/B85 @H-FDD | ||
| 46 | * Ultra-low power consumption | ||
| 47 | * Door Open/Close detect | ||
| 48 | * Door open/close statistics | ||
| 49 | * Datalog Feature | ||
| 50 | * Open Alarm Feature | ||
| 51 | * Multiply Sampling and one uplink | ||
| 52 | * Support Bluetooth v5.1 remote configure and update firmware | ||
| 53 | * Uplink on periodically | ||
| 54 | * Downlink to change configure | ||
| 55 | * 8500mAh Battery for long term use | ||
| 56 | * Nano SIM card slot for NB-IoT SIM | ||
| 57 | (% style="display:none" %) (%%) | ||
| 58 | |||
| 59 | == 1.3 Specification == | ||
| 60 | |||
| 61 | |||
| 62 | (% style="color:blue" %)**Common DC Characteristics:** | ||
| 63 | |||
| 64 | * Supply Voltage: 2.5v ~~ 3.6v | ||
| 65 | * Operating Temperature: -40 ~~ 85°C | ||
| 66 | |||
| 67 | (% style="color:blue" %)**NB-IoT Spec:** | ||
| 68 | |||
| 69 | (% style="color:#037691" %)**NB-IoT Module: BC660K-GL** | ||
| 70 | |||
| 71 | (% style="color:#037691" %)**Support Bands:** | ||
| 72 | |||
| 73 | * B1 @H-FDD: 2100MHz | ||
| 74 | * B2 @H-FDD: 1900MHz | ||
| 75 | * B3 @H-FDD: 1800MHz | ||
| 76 | * B4 @H-FDD: 2100MHz | ||
| 77 | * B5 @H-FDD: 860MHz | ||
| 78 | * B8 @H-FDD: 900MHz | ||
| 79 | * B12 @H-FDD: 720MHz | ||
| 80 | * B13 @H-FDD: 740MHz | ||
| 81 | * B17 @H-FDD: 730MHz | ||
| 82 | * B18 @H-FDD: 870MHz | ||
| 83 | * B19 @H-FDD: 870MHz | ||
| 84 | * B20 @H-FDD: 790MHz | ||
| 85 | * B25 @H-FDD: 1900MHz | ||
| 86 | * B28 @H-FDD: 750MHz | ||
| 87 | * B66 @H-FDD: 2000MHz | ||
| 88 | * B70 @H-FDD: 2000MHz | ||
| 89 | * B85 @H-FDD: 700MHz | ||
| 90 | |||
| 91 | (% style="color:blue" %)**Battery:** | ||
| 92 | |||
| 93 | * Li/SOCI2 un-chargeable battery | ||
| 94 | * Capacity: 8500mAh | ||
| 95 | * Self Discharge: <1% / Year @ 25°C | ||
| 96 | * Max continuously current: 130mA | ||
| 97 | * Max boost current: 2A, 1 second | ||
| 98 | |||
| 99 | (% style="color:blue" %)**Power Consumption** | ||
| 100 | |||
| 101 | * STOP Mode: 10uA @ 3.3v | ||
| 102 | * Max transmit power: 350mA@3.3v | ||
| 103 | (% style="display:none" %) (%%) | ||
| 104 | |||
| 105 | == 1.4 Applications == | ||
| 106 | |||
| 107 | |||
| 108 | [[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LDS03A%20-%20Outdoor%20LoRaWAN%20OpenClose%20Door%20Sensor%20Manual/WebHome/1654741400370-813.png?rev=1.1||alt="1654741400370-813.png"]] | ||
| 109 | |||
| 110 | |||
| 111 | == 1.5 Sleep mode and working mode == | ||
| 112 | |||
| 113 | |||
| 114 | (% style="color:blue" %)**Deep Sleep Mode: **(%%)Sensor doesn't have any NB-IoT activate. This mode is used for storage and shipping to save battery life. | ||
| 115 | |||
| 116 | (% style="color:blue" %)**Working Mode:** (%%)In this mode, Sensor will work as NB-IoT Sensor to Join NB-IoT network and send out sensor data to server. Between each sampling/tx/rx periodically, sensor will be in IDLE mode), in IDLE mode, sensor has the same power consumption as Deep Sleep mode. | ||
| 117 | |||
| 118 | |||
| 119 | == 1.6 Button & LEDs == | ||
| 120 | |||
| 121 | |||
| 122 | [[image:Main.User Manual for LoRaWAN End Nodes.D20-LBD22-LBD23-LB_LoRaWAN_Temperature_Sensor_User_Manual.WebHome@1675071855856-879.png]] | ||
| 123 | |||
| 124 | |||
| 125 | (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %) | ||
| 126 | |=(% style="width: 167px;background-color:#4F81BD;color:white" %)**Behavior on ACT**|=(% style="width: 117px;background-color:#4F81BD;color:white" %)**Function**|=(% style="width:225px;background-color:#4F81BD;color:white" %)**Action** | ||
| 127 | |(% style="width:167px" %)Pressing ACT between 1s < time < 3s|(% style="width:117px" %)Send an uplink|(% style="width:225px" %)((( | ||
| 128 | If sensor has already attached to NB-IoT network, sensor will send an uplink packet, (% style="color:blue" %)**blue led** (%%)will blink once. | ||
| 129 | Meanwhile, BLE module will be active and user can connect via BLE to configure device. | ||
| 130 | ))) | ||
| 131 | |(% style="width:167px" %)Pressing ACT for more than 3s|(% style="width:117px" %)Active Device|(% style="width:225px" %)((( | ||
| 132 | (% style="color:green" %)**Green led**(%%) will fast blink 5 times, device will enter (% style="color:#037691" %)**OTA mode**(%%) for 3 seconds. And then start to attach NB-IoT network. | ||
| 133 | (% style="color:green" %)**Green led**(%%) will solidly turn on for 5 seconds after joined in network. | ||
| 134 | Once sensor is active, BLE module will be active and user can connect via BLE to configure device, no matter if device attach NB-IoT network or not. | ||
| 135 | ))) | ||
| 136 | |(% style="width:167px" %)Fast press ACT 5 times.|(% style="width:117px" %)Deactivate Device|(% style="width:225px" %)(% style="color:red" %)**Red led**(%%) will solid on for 5 seconds. Means device is in Deep Sleep Mode. | ||
| 137 | |||
| 138 | (% style="color:red" %)**Note: When the device is executing a program, the buttons may become invalid. It is best to press the buttons after the device has completed the program execution.** | ||
| 139 | |||
| 140 | |||
| 141 | == 1.7 BLE connection == | ||
| 142 | |||
| 143 | |||
| 144 | DS03A-NB support BLE remote configure and firmware update. | ||
| 145 | |||
| 146 | |||
| 147 | BLE can be used to configure the parameter of sensor or see the console output from sensor. BLE will be only activate on below case: | ||
| 148 | |||
| 149 | * Press button to send an uplink | ||
| 150 | * Press button to active device. | ||
| 151 | * Device Power on or reset. | ||
| 152 | |||
| 153 | If there is no activity connection on BLE in 60 seconds, sensor will shut down BLE module to enter low power mode. | ||
| 154 | |||
| 155 | |||
| 156 | == 1.8 Pin Definitions & Switch == | ||
| 157 | |||
| 158 | |||
| 159 | [[image:image-20230819104805-5.png]] | ||
| 160 | |||
| 161 | |||
| 162 | === 1.8.1 Jumper JP2 === | ||
| 163 | |||
| 164 | |||
| 165 | Power on Device when put this jumper. | ||
| 166 | |||
| 167 | |||
| 168 | === 1.8.2 BOOT MODE / SW1 === | ||
| 169 | |||
| 170 | |||
| 171 | **1)** (% style="color:blue" %)**ISP**(%%): upgrade mode, device won't have any signal in this mode. but ready for upgrade firmware. LED won't work. Firmware won't run. | ||
| 172 | |||
| 173 | **2)** (% style="color:blue" %)**Flash**(%%): work mode, device starts to work and send out console output for further debug | ||
| 174 | |||
| 175 | |||
| 176 | === 1.8.3 Reset Button === | ||
| 177 | |||
| 178 | |||
| 179 | Press to reboot the device. | ||
| 180 | |||
| 181 | (% style="display:none" %) | ||
| 182 | |||
| 183 | |||
| 184 | == 1.9 Mechanical == | ||
| 185 | |||
| 186 | [[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/D20-LBD22-LBD23-LB_LoRaWAN_Temperature_Sensor_User_Manual/WebHome/1675143884058-338.png?rev=1.1||alt="1675143884058-338.png"]] | ||
| 187 | |||
| 188 | [[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/D20-LBD22-LBD23-LB_LoRaWAN_Temperature_Sensor_User_Manual/WebHome/1675143899218-599.png?rev=1.1||alt="1675143899218-599.png"]] | ||
| 189 | |||
| 190 | [[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/D20-LBD22-LBD23-LB_LoRaWAN_Temperature_Sensor_User_Manual/WebHome/1675143909447-639.png?rev=1.1||alt="1675143909447-639.png"]] | ||
| 191 | |||
| 192 | |||
| 193 | |||
| 194 | **Probe Mechanical:** | ||
| 195 | |||
| 196 | |||
| 197 | [[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LDS03A%20-%20Outdoor%20LoRaWAN%20OpenClose%20Door%20Sensor%20Manual/WebHome/1654741444887-479.png?width=513&height=399&rev=1.1||alt="1654741444887-479.png"]] | ||
| 198 | |||
| 199 | |||
| 200 | |||
| 201 | == 1.10 Magnet Distance == | ||
| 202 | |||
| 203 | |||
| 204 | * Wood Door: 10mm ~~ 30mm | ||
| 205 | * Iron Door: 30 ~~ 45mm | ||
| 206 | (% style="display:none" %) (%%) | ||
| 207 | |||
| 208 | = 2. Use DS03A-NB to communicate with IoT Server = | ||
| 209 | |||
| 210 | == 2.1 Send data to IoT server via NB-IoT network == | ||
| 211 | |||
| 212 | |||
| 213 | The DS03A-NB is equipped with a NB-IoT module, the pre-loaded firmware in DS03A-NB 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 DS03A-NB. | ||
| 214 | |||
| 215 | |||
| 216 | Below shows the network structure: | ||
| 217 | |||
| 218 | [[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/DS03A-NB_NB-IoT_Door_Sensor_User_Manual/WebHome/image-20231011093807-6.png?width=879&height=278&rev=1.1||alt="image-20231011093807-6.png"]] | ||
| 219 | |||
| 220 | |||
| 221 | There are two version: (% style="color:blue" %)**-GE**(%%) and (% style="color:blue" %)**-1D**(%%) version of DS03A-NB. | ||
| 222 | |||
| 223 | |||
| 224 | (% style="color:blue" %)**GE Version**(%%): This version doesn't include SIM card or point to any IoT server. User needs to use AT Commands to configure below two steps to set DS03A-NB send data to IoT server. | ||
| 225 | |||
| 226 | * Install NB-IoT SIM card and configure APN. See instruction of [[Attach Network>>url:http://wiki.dragino.com/xwiki/bin/view/Main/General%20Configure%20to%20Connect%20to%20IoT%20server%20for%20-NB%20%26%20-NS%20NB-IoT%20models/#H2.AttachNetwork]]. | ||
| 227 | |||
| 228 | * Set up sensor to point to IoT Server. See instruction of [[Configure to Connect Different Servers>>url:http://wiki.dragino.com/xwiki/bin/view/Main/General%20Configure%20to%20Connect%20to%20IoT%20server%20for%20-NB%20%26%20-NS%20NB-IoT%20models/#H3.Configuretoconnecttodifferentservers]]. | ||
| 229 | |||
| 230 | Below shows result of different server as a glance. | ||
| 231 | |||
| 232 | (% border="1" cellspacing="4" style="width:515px" %) | ||
| 233 | |(% style="background-color:#4f81bd; color:white; width:100px" %)**Servers**|(% style="background-color:#4f81bd; color:white; width:300px" %)**Dash Board**|(% style="background-color:#4f81bd; color:white; width:115px" %)**Comments** | ||
| 234 | |(% style="width:127px" %)[[Node-Red>>url:http://wiki.dragino.com/xwiki/bin/view/Main/General%20Configure%20to%20Connect%20to%20IoT%20server%20for%20-NB%20%26%20-NS%20NB-IoT%20models/#H3.5A0Node-RedA028viaA0MQTT29]]|(% style="width:385px" %)((( | ||
| 235 | (% style="text-align:center" %) | ||
| 236 | [[image:image-20230819113244-8.png||height="183" width="367"]] | ||
| 237 | )))|(% style="width:170px" %) | ||
| 238 | |(% style="width:127px" %)[[DataCake>>url:http://wiki.dragino.com/xwiki/bin/view/Main/General%20Configure%20to%20Connect%20to%20IoT%20server%20for%20-NB%20%26%20-NS%20NB-IoT%20models/#H3.4Datacake]]|(% style="width:385px" %)((( | ||
| 239 | (% style="text-align:center" %) | ||
| 240 | [[image:image-20230819113244-9.png||height="119" width="367"]] | ||
| 241 | )))|(% style="width:170px" %) | ||
| 242 | |(% style="width:127px" %)[[Tago.IO>>url:http://wiki.dragino.com/xwiki/bin/view/Main/General%20Configure%20to%20Connect%20to%20IoT%20server%20for%20-NB%20%26%20-NS%20NB-IoT%20models/#H3.7A0Tago.ioA028viaA0MQTT29]]|(% style="width:385px" %) |(% style="width:170px" %) | ||
| 243 | |(% style="width:127px" %)[[General UDP>>url:http://wiki.dragino.com/xwiki/bin/view/Main/General%20Configure%20to%20Connect%20to%20IoT%20server%20for%20-NB%20%26%20-NS%20NB-IoT%20models/#H3.1GeneralA0UDPA0Connection]]|(% style="width:385px" %)Raw Payload. Need Developer to design Dash Board|(% style="width:170px" %) | ||
| 244 | |(% style="width:127px" %)[[General MQTT>>url:http://wiki.dragino.com/xwiki/bin/view/Main/General%20Configure%20to%20Connect%20to%20IoT%20server%20for%20-NB%20%26%20-NS%20NB-IoT%20models/#H3.2GeneralA0MQTTA0Connection]]|(% style="width:385px" %)Raw Payload. Need Developer to design Dash Board|(% style="width:170px" %) | ||
| 245 | |(% style="width:127px" %)[[ThingSpeak>>url:http://wiki.dragino.com/xwiki/bin/view/Main/General%20Configure%20to%20Connect%20to%20IoT%20server%20for%20-NB%20%26%20-NS%20NB-IoT%20models/#H3.3A0ThingSpeakA028viaA0MQTT29]]|(% style="width:385px" %)((( | ||
| 246 | (% style="text-align:center" %) | ||
| 247 | [[image:image-20230819113244-10.png||height="104" width="367"]] | ||
| 248 | )))|(% style="width:170px" %) | ||
| 249 | |(% style="width:127px" %)[[ThingsBoard>>url:http://wiki.dragino.com/xwiki/bin/view/Main/General%20Configure%20to%20Connect%20to%20IoT%20server%20for%20-NB%20%26%20-NS%20NB-IoT%20models/#H3.6A0ThingsBoard.CloudA028viaA0MQTT29]]|(% style="width:385px" %)((( | ||
| 250 | (% style="text-align:center" %) | ||
| 251 | [[image:image-20230819113244-11.png||height="141" width="367"]] | ||
| 252 | )))|(% style="width:170px" %) | ||
| 253 | |||
| 254 | (% style="color:blue" %)**1D Version**(%%): This version has 1NCE SIM card pre-installed and configure to send value to DataCake. User Just need to select the sensor type in DataCake and Activate DS03A-NB and user will be able to see data in DataCake. See here for [[DataCake Config Instruction>>url:http://wiki.dragino.com/xwiki/bin/view/Main/General%20Configure%20to%20Connect%20to%20IoT%20server%20for%20-NB%20%26%20-NS%20NB-IoT%20models/#H3.4Datacake]]. | ||
| 255 | |||
| 256 | |||
| 257 | == 2.2 Payload Types == | ||
| 258 | |||
| 259 | |||
| 260 | To meet different server requirement, DS03A-NB supports different payload type. | ||
| 261 | |||
| 262 | **Includes:** | ||
| 263 | |||
| 264 | * [[General JSON format payload>>||anchor="H2.2.1GeneralJsonFormat28Type3D529"]]. (Type=5) | ||
| 265 | |||
| 266 | * [[HEX format Payload>>||anchor="H2.2.2HEXformatPayload28Type3D029"]]. (Type=0) | ||
| 267 | |||
| 268 | * [[ThingSpeak Format>>||anchor="H2.2.4ThingSpeakPayload28Type3D129"]]. (Type=1) | ||
| 269 | |||
| 270 | * [[ThingsBoard Format>>||anchor="H2.2.3ThingsBoardPayload28Type3D329"]]. (Type=3) | ||
| 271 | |||
| 272 | User can specify the payload type when choose the connection protocol. Example: | ||
| 273 | |||
| 274 | (% style="color:#037691" %)**AT+PRO=2,0** (%%) ~/~/ Use UDP Connection & hex Payload | ||
| 275 | |||
| 276 | (% style="color:#037691" %)**AT+PRO=2,5** (%%) ~/~/ Use UDP Connection & Json Payload | ||
| 277 | |||
| 278 | (% style="color:#037691" %)**AT+PRO=3,5 ** (%%) ~/~/ Use MQTT Connection & Json Payload | ||
| 279 | |||
| 280 | |||
| 281 | === 2.2.1 General Json Format(Type~=5) === | ||
| 282 | |||
| 283 | |||
| 284 | (% style="color:red" %)**This is the General Json Format. Payloads in General Json format for single-channel mode and double-channel mode have different byte lengths.** | ||
| 285 | |||
| 286 | |||
| 287 | **The General Json format payload for the single-channel mode is as follows:** | ||
| 288 | |||
| 289 | (% style="color:#4472c4" %)**{"IMEI":"866207052559857","Model":"DS03A-NB","level status":1,"alarm status":0,"door open num":0,"last open time":0,"level status2":1,"alarm status2":0,"door open num2":0,"last open time2":0,"battery":3.48,"signal":24,"1":{1,0,0,2023/11/13 09:59:01},"2":{0,0,261,2023/11/13 03:20:00},"3":{237,9896971,263,2023/11/13 03:05:00},"4":{0,29,263,2023/11/13 02:20:12},"5":{215,9897015,268,2023/11/13 01:58:16},"6":{0,79,261,2023/11/13 01:43:16},"7":{227,9896991,5368540,2023/11/13 01:18:46},"8":{0,19,5367640,2023/11/11 08:53:57}}** | ||
| 290 | |||
| 291 | [[image:image-20231115162221-7.png]] | ||
| 292 | |||
| 293 | |||
| 294 | **The General Json format payload for the double-channel mode is as follows:** | ||
| 295 | |||
| 296 | (% style="color:#4472c4" %)**{"IMEI":"866207058378443","Model":"DS03A-NB","level status":1,"alarm status":0,"door open num":2,"last open time":0,"level status2":1,"alarm status2":0,"door open num2":3,"last open time2":0,"battery":3.39,"signal":25,"1":{1,4,0,1,3,0,2023/11/15 07:54:30},"2":{1,3,0,1,6,1,2023/11/15 07:10:04},"3":{0,0,0,1,1,0,2023/11/15 06:55:04},"4":{0,0,0,1,0,0,2023/11/15 06:40:04},"5":{0,0,0,1,0,0,2023/11/15 03:50:36},"6":{0,0,0,1,4,11,2023/11/15 03:28:16},"7":{0,0,0,1,4,11,2023/11/15 03:13:16},"8":{0,0,0,1,3,11,2023/11/15 02:58:25}}** | ||
| 297 | |||
| 298 | [[image:image-20231115161803-6.png]] | ||
| 299 | |||
| 300 | |||
| 301 | (% style="color:red" %)**Notice, from above payload:** | ||
| 302 | |||
| 303 | * level status, alarm status, door open num, last open time, level status2, alarm status2, door open sum2, last open time2, Battery & Signal are the value at uplink time. | ||
| 304 | |||
| 305 | * Json entry 1 ~~ 8 are the last 1 ~~ 8 sampling data as specify by (% style="color:#037691" %)**AT+NOUD=8 ** (%%)Command. Each entry includes (from left to right): | ||
| 306 | |||
| 307 | Single-channel mode: level status, door open num, last open time, Sampling time. | ||
| 308 | |||
| 309 | Double-channel mode: level status, door open num, last open time, level status2, door open sum2, last open time2, Sampling time. | ||
| 310 | |||
| 311 | |||
| 312 | |||
| 313 | === 2.2.2 HEX format Payload(Type~=0) === | ||
| 314 | |||
| 315 | |||
| 316 | (% style="color:red" %)**This is the HEX Format. Payloads in HEX format for single-channel mode and double-channel mode have different byte lengths.** | ||
| 317 | |||
| 318 | |||
| 319 | **The HEX format payload for the single-channel mode is as follows:** | ||
| 320 | |||
| 321 | (% style="color:#4472c4" %)**f86620705255985712640d9c180101000000000000006551f424010000000000006551f36500000000000105655195e0ed97040b0001076551925c0000001d000107655187dcd797043700010c655182b80000004f00010565517f34e397041f51eadc655179760000001351e758654f4125** | ||
| 322 | |||
| 323 | [[image:image-20231114091247-2.png||height="186" width="1363"]] | ||
| 324 | |||
| 325 | |||
| 326 | If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data. | ||
| 327 | |||
| 328 | [[image:image-20231114094432-3.png]] | ||
| 329 | |||
| 330 | |||
| 331 | |||
| 332 | **The HEX format payload for the double-channel mode is as follows:** | ||
| 333 | |||
| 334 | (% style="color:#4472c4" %)**f86620705255985712640db71701010000000000000001000000000000006552d13401000000000000000000000000006551f365000000000001050000005f00005f655195e0ed97040b0001070000005c00005c6551925c0000001d00010700000033000033655187dcd797043700010c00000033000033655182b80000004f0001050000003300003365517f34e397041f51eadc00000000000000655179760000001351e75800000000000000654f4125** | ||
| 335 | |||
| 336 | [[image:image-20231114091229-1.png||height="180" width="1584"]] | ||
| 337 | |||
| 338 | |||
| 339 | If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data. | ||
| 340 | |||
| 341 | [[image:image-20231114094838-5.png]] | ||
| 342 | |||
| 343 | |||
| 344 | (% style="color:blue" %)**Version:** | ||
| 345 | |||
| 346 | These bytes include the hardware and software version. | ||
| 347 | |||
| 348 | (% style="color:#037691" %)**Higher byte:**(%%) Specify Sensor Model: 0x12 for DS03A-NB | ||
| 349 | |||
| 350 | (% style="color:#037691" %)**Lower byte:**(%%) Specify the software version: 0x64=100, means firmware version 1.0.0 | ||
| 351 | |||
| 352 | |||
| 353 | (% style="color:blue" %)**BAT (Battery Info):** | ||
| 354 | |||
| 355 | Ex1: 0x0dda = 3546mV | ||
| 356 | |||
| 357 | |||
| 358 | (% style="color:blue" %)**Signal Strength:** | ||
| 359 | |||
| 360 | NB-IoT Network signal Strength. | ||
| 361 | |||
| 362 | **Ex1: 0x15 = 21** | ||
| 363 | |||
| 364 | **0** -113dBm or less | ||
| 365 | |||
| 366 | **1** -111dBm | ||
| 367 | |||
| 368 | **2...30** -109dBm... -53dBm | ||
| 369 | |||
| 370 | **31** -51dBm or greater | ||
| 371 | |||
| 372 | **99** Not known or not detectable | ||
| 373 | |||
| 374 | |||
| 375 | (% style="color:blue" %)**Timestamp: ** | ||
| 376 | |||
| 377 | Unit Timestamp Example: 650abc40(H) = 1695202368(D) | ||
| 378 | |||
| 379 | Put the decimal value into this link([[https:~~/~~/www.epochconverter.com)>>https://www.epochconverter.com]]) to get the time. | ||
| 380 | |||
| 381 | |||
| 382 | === 2.2.3 ThingsBoard Payload(Type~=3) === | ||
| 383 | |||
| 384 | |||
| 385 | Type3 payload special design for ThingsBoard, it will also configure other default server to ThingsBoard. | ||
| 386 | |||
| 387 | (% style="color:#4472c4" %)**{ | ||
| 388 | "IMEI": "866207058378443", | ||
| 389 | "Model": "DS03A-NB", | ||
| 390 | "level status": 1, | ||
| 391 | "alarm status": 0, | ||
| 392 | "door open num": 6, | ||
| 393 | "last open time": 1, | ||
| 394 | "level status2": 1, | ||
| 395 | "alarm status2": 0, | ||
| 396 | "door open num2": 2, | ||
| 397 | "last open time2": 0, | ||
| 398 | "battery": 3.4, | ||
| 399 | "signal": 24 | ||
| 400 | }** | ||
| 401 | |||
| 402 | [[image:image-20231115150948-1.png||height="625" width="1188"]] | ||
| 403 | |||
| 404 | |||
| 405 | === 2.2.4 ThingSpeak Payload(Type~=1) === | ||
| 406 | |||
| 407 | |||
| 408 | This payload meets ThingSpeak platform requirement. It includes eight fields. Form 1~~8 are: | ||
| 409 | |||
| 410 | Distance, Battery & Signal. This payload type only valid for ThingsSpeak Platform | ||
| 411 | |||
| 412 | As below: | ||
| 413 | |||
| 414 | (% style="color:#4472c4" %)**field1=Flow value&field2=Battery value&field3=signal value** | ||
| 415 | |||
| 416 | [[image:image-20231115154757-2.png]] | ||
| 417 | |||
| 418 | [[image:image-20231115154821-3.png||height="695" width="1119"]] | ||
| 419 | |||
| 420 | |||
| 421 | |||
| 422 | == 2.3 Test Uplink and Change Update Interval == | ||
| 423 | |||
| 424 | |||
| 425 | By default, Sensor will send uplinks (% style="color:blue" %)**every 2 hours**(%%) & AT+NOUD=8 | ||
| 426 | |||
| 427 | User can use below commands to change the (% style="color:blue" %)**uplink interval**. | ||
| 428 | |||
| 429 | (% style="color:#037691" %)**AT+TDC=600 ** (%%) ~/~/ Set Update Interval to 600s | ||
| 430 | |||
| 431 | User can also push the button for more than 1 seconds to activate an uplink. | ||
| 432 | |||
| 433 | |||
| 434 | == 2.4 Multi-Samplings and One uplink == | ||
| 435 | |||
| 436 | |||
| 437 | To save battery life, DS03A-NB will sample Water Flow data every 15 minutes and send one uplink every 2 hours. So each uplink it will include 8 stored data + 1 real-time data. They are defined by: | ||
| 438 | |||
| 439 | * (% style="color:#037691" %)**AT+TR=900** (%%) ~/~/ The unit is seconds, and the default is to record data once every 900 seconds (15 minutes, the minimum can be set to 180 seconds) | ||
| 440 | |||
| 441 | * (% 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. | ||
| 442 | |||
| 443 | The diagram below explains the relationship between TR, NOUD, and TDC more clearly: | ||
| 444 | |||
| 445 | [[image:1692424376354-959.png]] | ||
| 446 | |||
| 447 | |||
| 448 | == 2.5 Trggier an uplink by external interrupt == | ||
| 449 | |||
| 450 | |||
| 451 | DS03A-NB has an external trigger interrupt function. Users can use the PB15 pin to trigger the upload of data packets. | ||
| 452 | |||
| 453 | (% style="color:blue" %)**AT command:** | ||
| 454 | |||
| 455 | * (% style="color:#037691" %)**AT+INTMOD **(%%) ~/~/ Set the trigger interrupt mode | ||
| 456 | |||
| 457 | * (% style="color:#037691" %)**AT+INTMOD=0 **(%%) ~/~/ Disable Interrupt | ||
| 458 | |||
| 459 | * (% style="color:#037691" %)**AT+INTMOD=1 **(%%) ~/~/ Trigger by rising and falling edge | ||
| 460 | |||
| 461 | * (% style="color:#037691" %)**AT+INTMOD=2 **(%%) ~/~/ Trigger by falling edge | ||
| 462 | |||
| 463 | * (% style="color:#037691" %)**AT+INTMOD=3 **(%%) ~/~/ Trigger by rising edge | ||
| 464 | (% style="display:none" %) (%%) | ||
| 465 | |||
| 466 | == 2.5 Set Transmit Interval Time == | ||
| 467 | |||
| 468 | |||
| 469 | ((( | ||
| 470 | Feature: Change NB-IoT End Node Transmit Interval. | ||
| 471 | ))) | ||
| 472 | |||
| 473 | ((( | ||
| 474 | (% style="color:blue" %)**AT Command: AT+TDC** | ||
| 475 | ))) | ||
| 476 | |||
| 477 | (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %) | ||
| 478 | |=(% style="width: 156px;background-color:#4F81BD;color:white" %)**Command Example**|=(% style="width: 137px;background-color:#4F81BD;color:white" %)**Function**|=(% style="background-color:#4F81BD;color:white" %)**Response** | ||
| 479 | |(% style="width:156px" %)AT+TDC=?|(% style="width:137px" %)Show current transmit Interval|((( | ||
| 480 | 30000 | ||
| 481 | OK | ||
| 482 | the interval is 30000ms = 30s | ||
| 483 | ))) | ||
| 484 | |(% style="width:156px" %)AT+TDC=60000|(% style="width:137px" %)Set Transmit Interval|((( | ||
| 485 | OK | ||
| 486 | Set transmit interval to 60000ms = 60 seconds | ||
| 487 | ))) | ||
| 488 | |||
| 489 | ((( | ||
| 490 | (% style="color:blue" %)**Downlink Command: 0x01** | ||
| 491 | ))) | ||
| 492 | |||
| 493 | ((( | ||
| 494 | Format: Command Code (0x01) followed by 3 bytes time value. | ||
| 495 | ))) | ||
| 496 | |||
| 497 | ((( | ||
| 498 | If the downlink payload=0100003C, it means set the END Node's Transmit Interval to 0x00003C=60(S), while type code is 01. | ||
| 499 | ))) | ||
| 500 | |||
| 501 | * ((( | ||
| 502 | Example 1: Downlink Payload: 0100001E ~/~/ Set Transmit Interval (TDC) = 30 seconds | ||
| 503 | ))) | ||
| 504 | * ((( | ||
| 505 | Example 2: Downlink Payload: 0100003C ~/~/ Set Transmit Interval (TDC) = 60 seconds | ||
| 506 | )))(% style="display:none" %) (%%) | ||
| 507 | |||
| 508 | == 2.7 Enable / Disable Alarm == | ||
| 509 | |||
| 510 | |||
| 511 | Feature: Enable/Disable Alarm for open/close event. Default value 0. | ||
| 512 | |||
| 513 | (% style="color:blue" %)**AT Command: ** | ||
| 514 | |||
| 515 | (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:515px" %) | ||
| 516 | |(% style="background-color:#4f81bd; color:white; width:153px" %)**Command Example**|(% style="background-color:#4f81bd; color:white; width:276px" %)**Function**|(% style="background-color:#4f81bd; color:white; width:86px" %)**Response** | ||
| 517 | |(% style="width:154px" %)AT+DISALARM=1|(% style="width:278px" %)End node will only send packets in TDC time.|OK | ||
| 518 | |(% style="width:154px" %)AT+DISALARM=0|(% style="width:278px" %)End node will send packets in TDC time or status change for door sensor|OK | ||
| 519 | |||
| 520 | (% style="color:blue" %)**Downlink Command: ** | ||
| 521 | |||
| 522 | 0xA7 01 ~/~/ Same As AT+DISALARM=1 | ||
| 523 | |||
| 524 | 0xA7 00 ~/~/ Same As AT+DISALARM=0 | ||
| 525 | |||
| 526 | |||
| 527 | == 2.8 Alarm Base on Timeout == | ||
| 528 | |||
| 529 | |||
| 530 | DS03A-NB can monitor the timeout for a status change, this feature can be used to monitor some events such as door opening too long etc. Related Parameters are: | ||
| 531 | |||
| 532 | * ((( | ||
| 533 | (% style="color:blue" %)**Keep Status: Status to be monitor** | ||
| 534 | ))) | ||
| 535 | |||
| 536 | (% style="color:#037691" %)**Keep Status = 1**(%%): Monitor Close to Open event | ||
| 537 | |||
| 538 | (% style="color:#037691" %)**Keep Status = 0**(%%): Monitor Open to Close event | ||
| 539 | |||
| 540 | |||
| 541 | * ((( | ||
| 542 | (% style="color:blue" %)**Keep Time: Timeout to send an Alarm** | ||
| 543 | ))) | ||
| 544 | |||
| 545 | Range 0 ~~ 65535(0xFFFF) seconds. | ||
| 546 | |||
| 547 | If (% style="color:#037691" %)**keep time = 0**(%%), Disable Alarm Base on Timeout feature. | ||
| 548 | |||
| 549 | If (% style="color:#037691" %)**keep time > 0**(%%), device will monitor the keep status event and send an alarm when status doesn't change after timeout. | ||
| 550 | |||
| 551 | |||
| 552 | * ((( | ||
| 553 | (% style="color:blue" %)**Downlink Command** | ||
| 554 | ))) | ||
| 555 | |||
| 556 | (% style="color:#037691" %)**Command: 0xA9 aa bb cc dd** | ||
| 557 | |||
| 558 | **A9:** Command Type Code | ||
| 559 | |||
| 560 | **aa: **01:TTRIG1; 02:TTRIG2 | ||
| 561 | |||
| 562 | **bb:** status to be monitored | ||
| 563 | |||
| 564 | **cc dd:** timeout. | ||
| 565 | |||
| 566 | |||
| 567 | **1) AT+TTRIG1 : (PA8 of pin)** | ||
| 568 | |||
| 569 | (% style="color:blue" %)**AT Command to configure:** | ||
| 570 | |||
| 571 | * ((( | ||
| 572 | (% style="color:#037691" %)**AT+TTRIG1=1,30** (%%) **~-~->** When the **Keep Status** change from close to open, and device remains in open status for more than 30 seconds. DS03A-NB will send an uplink packet, the Alarm1 bit(the second bit of 1^^st^^ byte of payload) on this uplink packet is set to 1. | ||
| 573 | |||
| 574 | (% style="color:#037691" %)**AT+TTRIG1=0,30** (%%) **~-~->** When the **Keep Status** change from open to close, and device remains in open status for more than 30 seconds. DS03A-NB will send an uplink packet, the Alarm1 bit (the second bit of 1^^st^^ byte of payload) on this uplink packet is set to 1. | ||
| 575 | ))) | ||
| 576 | |||
| 577 | * ((( | ||
| 578 | (% style="color:#037691" %)**AT+TTRIG1=0,0** (%%) **~-~-> ** Default Value, disable timeout Alarm. | ||
| 579 | |||
| 580 | |||
| 581 | ))) | ||
| 582 | |||
| 583 | (% style="color:blue" %)**Downlink Command to configure:** | ||
| 584 | |||
| 585 | If user send 0xA9 01 01 00 1E: equal to AT+TTRIG1=1,30 **or** 0xA9 01 00 00 00: Equal to AT+TTRIG1=0,0. | ||
| 586 | |||
| 587 | |||
| 588 | **2) AT+TTRIG2 : (PA4 of pin,need to use AT+TTRCHANNEL=2)** | ||
| 589 | |||
| 590 | (% style="color:blue" %)**AT Command to configure:** | ||
| 591 | |||
| 592 | * ((( | ||
| 593 | (% style="color:#037691" %)**AT+TTRIG2=1,30** (%%) **~-~->** When the **Keep Status** change from close to open, and device remains in open status for more than 30 seconds. DS03A-NB will send an uplink packet, the Alarm2 bit (the second bit of 12^^st^^ byte of payload) on this uplink packet is set to 1. | ||
| 594 | |||
| 595 | (% style="color:#037691" %)**AT+TTRIG2=0,30** (%%) **~-~->** When the **Keep Status** change from open to close, and device remains in open status for more than 30 seconds. DS03A-NB will send an uplink packet, the Alarm2 bit (the second bit of 12^^st^^ byte of payload) on this uplink packet is set to 1. | ||
| 596 | ))) | ||
| 597 | |||
| 598 | * ((( | ||
| 599 | (% style="color:#037691" %)**AT+TTRIG2=0,0** (%%) **~-~-> ** Default Value, disable timeout Alarm. | ||
| 600 | |||
| 601 | |||
| 602 | ))) | ||
| 603 | |||
| 604 | (% style="color:blue" %)**Downlink Command to configure:** | ||
| 605 | |||
| 606 | If user send 0xA9 02 00 00 1E: equal to AT+TTRIG2=0,30 **or** 0xA9 02 00 00 00: Equal to AT+TTRIG2=0,0. | ||
| 607 | |||
| 608 | |||
| 609 | == 2.9 TTRIG1 & TTRIG2 timeout status alarm == | ||
| 610 | |||
| 611 | |||
| 612 | It needs to be used with AT+TTRIG1 or AT+TTRIG2. When TTRIG1 or TTRIG2 times out and causes an alarm, and the status does not change subsequently, an alarm packet will be sent at the alarm interval. | ||
| 613 | |||
| 614 | (% style="color:blue" %)**AT Command:** | ||
| 615 | |||
| 616 | (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %) | ||
| 617 | |=(% style="width: 155px;background-color:#4F81BD;color:white" %)**Command Example**|=(% style="width: 279px;background-color:#4F81BD;color:white" %)**Function**|=(% style="width: 76px;background-color:#4F81BD;color:white" %)**Response** | ||
| 618 | |(% style="width:155px" %)((( | ||
| 619 | AT+TTRALARM=0 | ||
| 620 | )))|(% style="width:279px" %)((( | ||
| 621 | disable continuous alarm | ||
| 622 | )))|(% style="width:84px" %)((( | ||
| 623 | OK | ||
| 624 | ))) | ||
| 625 | |(% style="width:155px" %)((( | ||
| 626 | AT+TTRALARM=60 | ||
| 627 | )))|(% style="width:279px" %)((( | ||
| 628 | The alarm interval is 60 minutes (unit: minutes) | ||
| 629 | )))|(% style="width:84px" %)((( | ||
| 630 | OK | ||
| 631 | ))) | ||
| 632 | |||
| 633 | (% style="color:blue" %)**Downlink Command:** | ||
| 634 | |||
| 635 | Example: 0C aa => AT+TTRALARM= aa | ||
| 636 | |||
| 637 | |||
| 638 | == 2.10 Count Mod == | ||
| 639 | |||
| 640 | |||
| 641 | Feature: Manually set the count mode. | ||
| 642 | |||
| 643 | (% style="color:blue" %)**AT Command:** | ||
| 644 | |||
| 645 | (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:515px" %) | ||
| 646 | |=(% style="width: 154px;background-color:#4F81BD;color:white" %)**Command Example**|=(% style="width: 275px;background-color:#4F81BD;color:white" %)**Function**|=(% style="width: 86px;background-color:#4F81BD;color:white" %)**Response** | ||
| 647 | |(% style="width:155px" %)((( | ||
| 648 | AT+COUNTMOD=0 | ||
| 649 | )))|(% style="width:277px" %)((( | ||
| 650 | the count value keeps accumulating mode | ||
| 651 | )))|(% style="width:86px" %)((( | ||
| 652 | OK | ||
| 653 | ))) | ||
| 654 | |(% style="width:155px" %)((( | ||
| 655 | AT+COUNTMOD=1 | ||
| 656 | )))|(% style="width:277px" %)((( | ||
| 657 | the count value will be reset after each TDC time(Last Close Duration Reset after each uplink) | ||
| 658 | )))|(% style="width:86px" %)((( | ||
| 659 | OK | ||
| 660 | ))) | ||
| 661 | |||
| 662 | (% style="color:blue" %)**Downlink Command:** | ||
| 663 | |||
| 664 | Example: 0B aa => AT+COUNTMOD = second byte | ||
| 665 | |||
| 666 | |||
| 667 | == 2.11 Number of channel of door sensors == | ||
| 668 | |||
| 669 | |||
| 670 | Feature: Set the number of door sensor channels. | ||
| 671 | |||
| 672 | (% style="color:blue" %)**AT Command:** | ||
| 673 | |||
| 674 | (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:500px" %) | ||
| 675 | |=(% style="width: 155px;background-color:#4F81BD;color:white" %)**Command Example**|=(% style="width: 288px; background-color:#4F81BD;color:white" %)**Function**|=(% style="width: 57px;background-color:#4F81BD;color:white" %)**Response** | ||
| 676 | |(% style="width:155px" %)((( | ||
| 677 | AT+TTRCHANNEL=1 | ||
| 678 | )))|(% style="width:259px" %)((( | ||
| 679 | Set as single channel, only use PA8 pin as interrupt pin. | ||
| 680 | )))|(% style="width:44px" %)((( | ||
| 681 | OK | ||
| 682 | ))) | ||
| 683 | |(% style="width:155px" %)((( | ||
| 684 | AT+TTRCHANNEL=2 | ||
| 685 | )))|(% style="width:259px" %)((( | ||
| 686 | Set as dual channel, use PA8 pin and PA4 pin as interrupt pin. | ||
| 687 | )))|(% style="width:44px" %)((( | ||
| 688 | OK | ||
| 689 | ))) | ||
| 690 | |||
| 691 | (% style="color:blue" %)**Downlink Command:** | ||
| 692 | |||
| 693 | Example: 0D aa => AT+TTRCHANNEL = second byte | ||
| 694 | |||
| 695 | |||
| 696 | == 2.12 Clear the open door times and the duration of the last open door == | ||
| 697 | |||
| 698 | |||
| 699 | (% style="color:blue" %)**AT Command:** | ||
| 700 | |||
| 701 | (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %) | ||
| 702 | |=(% style="width: 163px;background-color:#4F81BD;color:white" %)**Command Example**|=(% style="width: 290px; background-color:#4F81BD;color:white" %)**Function**|=(% style="width: 57px;background-color:#4F81BD;color:white" %)**Response** | ||
| 703 | |(% style="width:155px" %)AT+CLRC|(% style="width:259px" %)clear the open door times and the duration of the last open door.|(% style="width:44px" %)((( | ||
| 704 | OK | ||
| 705 | ))) | ||
| 706 | |||
| 707 | (% style="color:blue" %)**Downlink Command:**(%%)0xA6 01 | ||
| 708 | |||
| 709 | The sensor will clear the open door times and the duration of the last open door. | ||
| 710 | |||
| 711 | |||
| 712 | == 2.13 Set the count value of the number of open door == | ||
| 713 | |||
| 714 | |||
| 715 | (% style="color:blue" %)**AT Command:** | ||
| 716 | |||
| 717 | (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:500px" %) | ||
| 718 | |=(% style="width: 155px;background-color:#4F81BD;color:white" %)**Command Example**|=(% style="width: 288px; background-color:#4F81BD;color:white" %)**Function**|=(% style="width: 57px;background-color:#4F81BD;color:white" %)**Response** | ||
| 719 | |(% style="width:155px" %)((( | ||
| 720 | AT+SETCNT=1,100 | ||
| 721 | )))|(% style="width:259px" %)((( | ||
| 722 | Set the open door times of PA8 pin to 100 times. | ||
| 723 | )))|(% style="width:44px" %)((( | ||
| 724 | OK | ||
| 725 | ))) | ||
| 726 | |(% style="width:155px" %)AT+SETCNT=1,0|(% style="width:259px" %)Clear the open door times of PA8 pin.|(% style="width:44px" %)OK | ||
| 727 | |(% style="width:155px" %)((( | ||
| 728 | AT+SETCNT=2,50 | ||
| 729 | )))|(% style="width:259px" %)((( | ||
| 730 | Set the open door times of PA4 pin to 100 times. | ||
| 731 | )))|(% style="width:44px" %)((( | ||
| 732 | OK | ||
| 733 | ))) | ||
| 734 | |||
| 735 | (% style="color:blue" %)**Downlink Command:** | ||
| 736 | |||
| 737 | 0xA6 01 00 00 64 ==> AT+SETCNT=1,100 | ||
| 738 | |||
| 739 | 0xA6 01 00 00 00 ==> AT+SETCNT=1,0 | ||
| 740 | |||
| 741 | 0xA6 02 00 00 32 ==> AT+SETCNT=2,50 | ||
| 742 | |||
| 743 | |||
| 744 | = 3. Configure DS03A-NB = | ||
| 745 | |||
| 746 | == 3.1 Configure Methods == | ||
| 747 | |||
| 748 | |||
| 749 | DS03A-NB supports below configure method: | ||
| 750 | |||
| 751 | * AT Command via Bluetooth Connection (**Recommended**): [[BLE Configure Instruction>>http://wiki.dragino.com/xwiki/bin/view/Main/BLE%20Bluetooth%20Remote%20Configure/]]. | ||
| 752 | |||
| 753 | * AT Command via UART Connection : See [[UART Connection>>http://wiki.dragino.com/xwiki/bin/view/Main/UART%20Access%20for%20LoRa%20ST%20v4%20base%20model/#H2.3UARTConnectionforSN50v3basemotherboard]]. | ||
| 754 | (% style="display:none" %) (%%) | ||
| 755 | |||
| 756 | == 3.2 AT Commands Set == | ||
| 757 | |||
| 758 | |||
| 759 | AT+<CMD>? : Help on <CMD> | ||
| 760 | |||
| 761 | AT+<CMD> : Run <CMD> | ||
| 762 | |||
| 763 | AT+<CMD>=<value> : Set the value | ||
| 764 | |||
| 765 | AT+<CMD>=? : Get the value | ||
| 766 | |||
| 767 | |||
| 768 | (% style="color:blue" %)**General Commands** | ||
| 769 | |||
| 770 | AT : Attention | ||
| 771 | |||
| 772 | AT? : Short Help | ||
| 773 | |||
| 774 | ATZ : MCU Reset | ||
| 775 | |||
| 776 | AT+TDC : Application Data Transmission Interval | ||
| 777 | |||
| 778 | AT+CFG : Print all configurations | ||
| 779 | |||
| 780 | AT+CFGMOD : Working mode selection | ||
| 781 | |||
| 782 | AT+DEUI : Get or set the Device ID | ||
| 783 | |||
| 784 | AT+INTMOD : Set the trigger interrupt mode | ||
| 785 | |||
| 786 | AT+5VT : Set extend the time of 5V power | ||
| 787 | |||
| 788 | AT+PRO : Choose agreement | ||
| 789 | |||
| 790 | AT+RXDL : Extend the sending and receiving time | ||
| 791 | |||
| 792 | AT+DNSCFG : Get or Set DNS Server | ||
| 793 | |||
| 794 | AT+GETSENSORVALUE : Returns the current sensor measurement | ||
| 795 | |||
| 796 | AT+NOUD : Get or Set the number of data to be uploaded | ||
| 797 | |||
| 798 | AT+CDP : Read or Clear cached data | ||
| 799 | |||
| 800 | AT+SHTEMP: Get or Set alarm of temp | ||
| 801 | |||
| 802 | AT+SHHUM: Get or Set alarm of moisture | ||
| 803 | |||
| 804 | AT+SERVADDR : Server Address | ||
| 805 | |||
| 806 | |||
| 807 | (% style="color:blue" %)**UDP Management** | ||
| 808 | |||
| 809 | AT+CFM : Upload confirmation mode (only valid for UDP) | ||
| 810 | |||
| 811 | |||
| 812 | (% style="color:blue" %)**MQTT Management** | ||
| 813 | |||
| 814 | AT+CLIENT : Get or Set MQTT client | ||
| 815 | |||
| 816 | AT+UNAME : Get or Set MQTT Username | ||
| 817 | |||
| 818 | AT+PWD : Get or Set MQTT password | ||
| 819 | |||
| 820 | AT+PUBTOPIC : Get or Set MQTT publish topic | ||
| 821 | |||
| 822 | AT+SUBTOPIC : Get or Set MQTT subscription topic | ||
| 823 | |||
| 824 | |||
| 825 | (% style="color:blue" %)**Information** | ||
| 826 | |||
| 827 | AT+FDR : Factory Data Reset | ||
| 828 | |||
| 829 | AT+PWORD : Serial Access Password | ||
| 830 | |||
| 831 | AT+LDATA : Get the last upload data | ||
| 832 | |||
| 833 | AT+CDP : Read or Clear cached data | ||
| 834 | |||
| 835 | |||
| 836 | = 4. Battery & Power Consumption = | ||
| 837 | |||
| 838 | |||
| 839 | DS03A-NB use ER26500 + SPC1520 battery pack. See below link for detail information about the battery info and how to replace. | ||
| 840 | |||
| 841 | [[**Battery Info & Power Consumption Analyze**>>http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20calculate%20the%20battery%20life%20of%20Dragino%20sensors%3F/]] . | ||
| 842 | |||
| 843 | |||
| 844 | = 5. Firmware update = | ||
| 845 | |||
| 846 | |||
| 847 | User can change device firmware to:: | ||
| 848 | |||
| 849 | * Update with new features. | ||
| 850 | |||
| 851 | * Fix bugs. | ||
| 852 | |||
| 853 | Firmware and changelog can be downloaded from : **[[Firmware download link>>https://www.dropbox.com/sh/zbsm9p4coksqwd5/AADy2ZJc39KsvfbhTMCUGmz1a?dl=0]]** | ||
| 854 | |||
| 855 | Methods to Update Firmware: | ||
| 856 | |||
| 857 | * (Recommended way) OTA firmware update via BLE: [[**Instruction**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/BLE_Firmware_Update_NB_Sensors_BC660K-GL/]]. | ||
| 858 | |||
| 859 | * Update through UART TTL interface : **[[Instruction>>url:http://wiki.dragino.com/xwiki/bin/view/Main/UART%20Access%20for%20LoRa%20ST%20v4%20base%20model/#H1.LoRaSTv4baseHardware]]**. | ||
| 860 | (% style="display:none" %) (%%) | ||
| 861 | |||
| 862 | = 6. FAQ = | ||
| 863 | |||
| 864 | == 6.1 How can I access t BC660K-GL AT Commands? == | ||
| 865 | |||
| 866 | |||
| 867 | User can access to BC660K-GL directly and send AT Commands. | ||
| 868 | |||
| 869 | [[See BC660K-GL AT Command set>>url:https://www.dropbox.com/sh/5f6ssda5fum8rvs/AABT68l8ZzWOvZ5eg2qwOoFda?dl=0]] | ||
| 870 | |||
| 871 | |||
| 872 | = 7. Order Info = | ||
| 873 | |||
| 874 | |||
| 875 | Part Number: (% style="color:blue" %)**DS03A-NB-XX** | ||
| 876 | |||
| 877 | (% style="color:red" %)**XX**(%%): | ||
| 878 | |||
| 879 | * (% style="color:#037691" %)**GE**(%%): General version ( Exclude SIM card) | ||
| 880 | |||
| 881 | * (% style="color:#037691" %)**1D**(%%): with 1NCE* 10 years 500MB SIM card and Pre-configure to DataCake server | ||
| 882 | |||
| 883 | (% style="color:#037691" %)**1NCE SIM Card NB-IoT network coverage**(%%): Austria, Belgium, Bulgaria, Croatia, Czech Republic, Denmark, Finland, Germany, Great Britain, Greece, Hungary, Ireland, Italy, Latvia, Malta, Netherlands, Norway, Puerto Rico, Russia, Slovak , Republic, Slovenia, Spain, Sweden, Switzerland, Taiwan, USA, US Virgin Islands | ||
| 884 | |||
| 885 | |||
| 886 | = 8. Packing Info = | ||
| 887 | |||
| 888 | |||
| 889 | (% style="color:#037691" %)**Package Includes**: | ||
| 890 | |||
| 891 | * DS03A-NB NB-IoT Door sensor x 1 | ||
| 892 | |||
| 893 | * External antenna x 1 | ||
| 894 | |||
| 895 | (% style="color:#037691" %)**Dimension and weight**: | ||
| 896 | |||
| 897 | * Device Size: 13.0 x 5 x 4.5 cm | ||
| 898 | |||
| 899 | * Device Weight: 150g | ||
| 900 | |||
| 901 | * Package Size / pcs : 14.0 x 8x 5 cm | ||
| 902 | |||
| 903 | * Weight / pcs : 180g | ||
| 904 | (% style="display:none" %) (%%) | ||
| 905 | |||
| 906 | = 9. Support = | ||
| 907 | |||
| 908 | |||
| 909 | * 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. | ||
| 910 | |||
| 911 | * 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.cc>>mailto:Support@dragino.cc]]. | ||
| 912 | |||
| 913 | (% style="display:none" %) (%%) |