Changes for page wiki_test
Last modified by Mengting Qiu on 2024/09/05 17:35
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -22,19 +22,19 @@ 22 22 23 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 24 25 -DS03A- LB supports (% style="color:blue" %)**Datalog Feature,** (%%)it can save the data when there is no NB-IoT network and uplink when network recover.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 26 27 -DS03A- LB 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.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 28 29 -DS03A- LB is designed for outdoor use. It has a weatherproof enclosure and industrial level battery to work in low to high temperatures29 +DS03A-NB is designed for outdoor use. It has a weatherproof enclosure and industrial level battery to work in low to high temperatures 30 30 31 -S W3L-NB supports different uplink methods including (% style="color:blue" %)**MQTT, MQTTs, UDP & TCP**(%%) for different application requirement, and support uplinks to various IoT Servers.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 32 33 -S W3L-NB (% style="color:blue" %)**supports BLE configure **(%%)and(% style="color:blue" %)** OTA update**(%%) which make user easy to use.33 +DS03A-NB (% style="color:blue" %)**supports BLE configure **(%%)and(% style="color:blue" %)** OTA update**(%%) which make user easy to use. 34 34 35 -S W3L-NB is powered by (% style="color:blue" %)**8500mAh Li-SOCI2 battery**(%%), it is designed for long-term use up to several years.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 36 37 -S W3L-NB has optional built-in SIM card and default IoT server connection version. Which makes it works with simple configuration.37 +DS03A-NB has optional built-in SIM card and default IoT server connection version. Which makes it works with simple configuration. 38 38 39 39 [[image:image-20231011093807-6.png||height="278" width="879"]] 40 40 ... ... @@ -141,7 +141,7 @@ 141 141 == 1.7 BLE connection == 142 142 143 143 144 -S W3L-NB support BLE remote configure and firmware update.144 +DS03A-NB support BLE remote configure and firmware update. 145 145 146 146 147 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: ... ... @@ -211,7 +211,7 @@ 211 211 == 2.1 Send data to IoT server via NB-IoT network == 212 212 213 213 214 -The S W3L-NB is equipped with a NB-IoT module, the pre-loaded firmware in SW3L-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 SW3L-NB.214 +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. 215 215 216 216 217 217 Below shows the network structure: ... ... @@ -219,10 +219,10 @@ 219 219 [[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"]] 220 220 221 221 222 -There are two version: (% style="color:blue" %)**-GE**(%%) and (% style="color:blue" %)**-1D**(%%) version of S W3L-NB.222 +There are two version: (% style="color:blue" %)**-GE**(%%) and (% style="color:blue" %)**-1D**(%%) version of DS03A-NB. 223 223 224 224 225 -(% 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 S W3L-NB send data to IoT server.225 +(% 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. 226 226 227 227 * 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]]. 228 228 ... ... @@ -252,13 +252,13 @@ 252 252 [[image:image-20230819113244-11.png||height="141" width="367"]] 253 253 )))|(% style="width:170px" %) 254 254 255 -(% 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 S W3L-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 +(% 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]]. 256 256 257 257 258 258 == 2.2 Payload Types == 259 259 260 260 261 -To meet different server requirement, S W3L-NB supports different payload type.261 +To meet different server requirement, DS03A-NB supports different payload type. 262 262 263 263 **Includes:** 264 264 ... ... @@ -284,7 +284,7 @@ 284 284 285 285 This is the General Json Format. As below: 286 286 287 -(% style="color:#4472c4" %)**{"IMEI":"866207058378443","Model":"S W3L-NB","flow":217,"battery":3.54,"signal":24,"1":{221,2023/09/20 09:47:01},"2":{0,2023/09/20 09:15:04},"3":{0,2023/09/20 09:00:04},"4":{0,2023/09/20 08:45:03},"5":{0,2023/09/20 08:30:03},"6":{0,2023/09/20 08:15:03},"7":{0,2023/09/20 08:00:04},"8":{0,2023/09/20 07:45:04}}**287 +(% style="color:#4472c4" %)**{"IMEI":"866207058378443","Model":"DS03A-NB","flow":217,"battery":3.54,"signal":24,"1":{221,2023/09/20 09:47:01},"2":{0,2023/09/20 09:15:04},"3":{0,2023/09/20 09:00:04},"4":{0,2023/09/20 08:45:03},"5":{0,2023/09/20 08:30:03},"6":{0,2023/09/20 08:15:03},"7":{0,2023/09/20 08:00:04},"8":{0,2023/09/20 07:45:04}}** 288 288 289 289 290 290 [[image:image-20230920175015-3.png||height="613" width="890"]] ... ... @@ -315,7 +315,7 @@ 315 315 316 316 These bytes include the hardware and software version. 317 317 318 -(% style="color:#037691" %)**Higher byte:**(%%) Specify Sensor Model: 0x1 1for SW3L-NB318 +(% style="color:#037691" %)**Higher byte:**(%%) Specify Sensor Model: 0x12 for DS03A-NB 319 319 320 320 (% style="color:#037691" %)**Lower byte:**(%%) Specify the software version: 0x64=100, means firmware version 1.0.0 321 321 ... ... @@ -354,7 +354,7 @@ 354 354 355 355 Type3 payload special design for ThingsBoard, it will also configure other default server to ThingsBoard. 356 356 357 -(% style="color:#4472c4" %)** {"IMEI": "866207058378443","Model": "S W3L","flow": 502,"battery": 3.57,"signal": 23}**357 +(% style="color:#4472c4" %)** {"IMEI": "866207058378443","Model": "DS03A","flow": 502,"battery": 3.57,"signal": 23}** 358 358 359 359 [[image:image-20230922094043-2.png||height="558" width="851"]] 360 360 ... ... @@ -379,7 +379,7 @@ 379 379 === 2.3.2 Sensor Configuration, FPORT~=4 === 380 380 381 381 382 -DS03A- LB will only send this command after getting the downlink command **(0x26 02)** from the server.382 +DS03A-NB will only send this command after getting the downlink command **(0x26 02)** from the server. 383 383 384 384 (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:515px" %) 385 385 |(% colspan="8" style="background-color:#d9e2f3; color:#0070c0; width:515px" %)**Sensor Configuration FPORT=4** ... ... @@ -410,9 +410,9 @@ 410 410 (% style="color:blue" %)**Disalarm: (default: 0)** 411 411 ))) 412 412 413 - **If Disalarm = 1**, DS03A- LB will only send uplink at every TDC periodically. This is normally use for pulse meter application, in this application, there are many open/close event, and platform only care about the total number of pulse.413 + **If Disalarm = 1**, DS03A-NB will only send uplink at every TDC periodically. This is normally use for pulse meter application, in this application, there are many open/close event, and platform only care about the total number of pulse. 414 414 415 - **If Disalarm = 0**, DS03A- LB will send uplink at every TDC periodically and send data on each open/close event. This is useful for the application user need to monitor the open/close event in real-time.415 + **If Disalarm = 0**, DS03A-NB will send uplink at every TDC periodically and send data on each open/close event. This is useful for the application user need to monitor the open/close event in real-time. 416 416 417 417 418 418 (% style="color:red" %)** Note: When Disalarm=0, a high frequently open/close event will cause lots of uplink and drain battery very fast. ** ... ... @@ -436,7 +436,7 @@ 436 436 === 2.3.3 Real-Time Open/Close Status, Uplink FPORT~=2 === 437 437 438 438 439 -DS03A- LB will send this uplink **after** Device Status once join the LoRaWAN network successfully. And DS03A-LB will send uplinks when:439 +DS03A-NB will send this uplink **after** Device Status once join the LoRaWAN network successfully. And DS03A-NB will send uplinks when: 440 440 441 441 * Every 2 hours, this interval [[can be changed>>||anchor="H3.3.1A0SetTransmitIntervalTime"]]. 442 442 * There is an Open/Close event. (This info can be disabled by AT+DISALARM=1) ... ... @@ -612,7 +612,7 @@ 612 612 === 2.3.4 Historical Door Open/Close Event, FPORT~=3 === 613 613 614 614 615 -DS03A- LB stores sensor values and users can retrieve these history values via the [[downlink command>>||anchor="H2.5DatalogFeature"]].615 +DS03A-NB stores sensor values and users can retrieve these history values via the [[downlink command>>||anchor="H2.5DatalogFeature"]]. 616 616 617 617 The historical payload includes one or multiplies entries and every entry has the same payload as Real-Time open/close status. 618 618 ... ... @@ -640,7 +640,7 @@ 640 640 ))) 641 641 642 642 * ((( 643 -Each data entry is 11 bytes and has the same structure as [[Real-Time open/close status>>||anchor="H2.3.3A0Real-TimeOpen2FCloseStatus2CUplinkFPORT3D2"]], to save airtime and battery, DS03A- LB will send max bytes according to the current DR and Frequency bands.643 +Each data entry is 11 bytes and has the same structure as [[Real-Time open/close status>>||anchor="H2.3.3A0Real-TimeOpen2FCloseStatus2CUplinkFPORT3D2"]], to save airtime and battery, DS03A-NB will send max bytes according to the current DR and Frequency bands. 644 644 ))) 645 645 646 646 For example, in the US915 band, the max payload for different DR is: ... ... @@ -661,7 +661,7 @@ 661 661 **4. DR3**: total payload includes 22 entries of data. 662 662 ))) 663 663 664 -If DS03A- LB doesn't have any data in the polling time. It will uplink 11 bytes of 0664 +If DS03A-NB doesn't have any data in the polling time. It will uplink 11 bytes of 0 665 665 666 666 [[image:image-20230630155556-4.png||height="146" width="938"]] 667 667