Changes for page wiki_test

Last modified by Mengting Qiu on 2024/09/05 17:35

From 107.8 to 107.9 From 107.11 to 107.12

From version 107.9

edited by Xiaoling
on 2023/10/11 11:18

Change comment: There is no comment for this version

To version 107.11

edited by Xiaoling
on 2023/10/11 11:50

Change comment: There is no comment for this version

Raw
Rendered

Summary

Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

@@ -22,19 +22,19 @@
  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.
--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.
++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.
--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.
++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.
--DS03A-LB is designed for outdoor use. It has a weatherproof enclosure and industrial level battery to work in low to high temperatures
++DS03A-NB is designed for outdoor use. It has a weatherproof enclosure and industrial level battery to work in low to high temperatures
--SW3L-NB supports different uplink methods including (% style="color:blue" %)**MQTT, MQTTs, UDP & TCP**(%%) for different application requirement, and support uplinks to various IoT Servers.
++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.
--SW3L-NB (% style="color:blue" %)**supports BLE configure **(%%)and(% style="color:blue" %)** OTA update**(%%) which make user easy to use.
++DS03A-NB (% style="color:blue" %)**supports BLE configure **(%%)and(% style="color:blue" %)** OTA update**(%%) which make user easy to use.
--SW3L-NB is powered by (% style="color:blue" %)**8500mAh Li-SOCI2 battery**(%%), it is designed for long-term use up to several years.
++DS03A-NB is powered by (% style="color:blue" %)**8500mAh Li-SOCI2 battery**(%%), it is designed for long-term use up to several years.
--SW3L-NB has optional built-in SIM card and default IoT server connection version. Which makes it works with simple configuration.
++DS03A-NB has optional built-in SIM card and default IoT server connection version. Which makes it works with simple configuration.
  [[image:image-20231011093807-6.png||height="278" width="879"]]
@@ -141,7 +141,7 @@
  == 1.7 BLE connection ==
--SW3L-NB support BLE remote configure and firmware update.
++DS03A-NB support BLE remote configure and firmware update.
  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 @@
  == 2.1 Send data to IoT server via NB-IoT network ==
--The SW3L-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.
++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.
  Below shows the network structure:
@@ -219,10 +219,10 @@
  [[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"]]
--There are two version: (% style="color:blue" %)**-GE**(%%) and (% style="color:blue" %)**-1D**(%%) version of SW3L-NB.
++There are two version: (% style="color:blue" %)**-GE**(%%) and (% style="color:blue" %)**-1D**(%%) version of DS03A-NB.
--(% 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 SW3L-NB send data to IoT server.
++(% 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.
  * 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]].
@@ -252,13 +252,13 @@
  [[image:image-20230819113244-11.png||height="141" width="367"]]
  )))|(% style="width:170px" %)
--(% 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 SW3L-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]].
++(% 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]].
  == 2.2 Payload Types ==
--To meet different server requirement, SW3L-NB supports different payload type.
++To meet different server requirement, DS03A-NB supports different payload type.
  **Includes:**
@@ -284,7 +284,7 @@
  This is the General Json Format. As below:
--(% style="color:#4472c4" %)**{"IMEI":"866207058378443","Model":"SW3L-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}}**
++(% 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}}**
  [[image:image-20230920175015-3.png||height="613" width="890"]]
@@ -315,7 +315,7 @@
  These bytes include the hardware and software version.
--(% style="color:#037691" %)**Higher byte:**(%%) Specify Sensor Model: 0x11 for SW3L-NB
++(% style="color:#037691" %)**Higher byte:**(%%) Specify Sensor Model: 0x12 for DS03A-NB
  (% style="color:#037691" %)**Lower byte:**(%%) Specify the software version: 0x64=100, means firmware version 1.0.0
@@ -354,7 +354,7 @@
  Type3 payload special design for ThingsBoard, it will also configure other default server to ThingsBoard.
--(% style="color:#4472c4" %)** {"IMEI": "866207058378443","Model": "SW3L","flow": 502,"battery": 3.57,"signal": 23}**
++(% style="color:#4472c4" %)** {"IMEI": "866207058378443","Model": "DS03A","flow": 502,"battery": 3.57,"signal": 23}**
  [[image:image-20230922094043-2.png||height="558" width="851"]]
@@ -379,7 +379,7 @@
  === 2.3.2  Sensor Configuration, FPORT~=4 ===
--DS03A-LB will only send this command after getting the downlink command **(0x26 02)** from the server.
++DS03A-NB will only send this command after getting the downlink command **(0x26 02)** from the server.
  (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:515px" %)
  |(% colspan="8" style="background-color:#d9e2f3; color:#0070c0; width:515px" %)**Sensor Configuration FPORT=4**
@@ -410,9 +410,9 @@
  (% style="color:blue" %)**Disalarm: (default: 0)**
  )))
-- **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.
++ **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.
-- **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.
++ **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.
  (% 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 @@
  === 2.3.3  Real-Time Open/Close Status, Uplink FPORT~=2 ===
--DS03A-LB will send this uplink **after** Device Status once join the LoRaWAN network successfully. And DS03A-LB will send uplinks when:
++DS03A-NB will send this uplink **after** Device Status once join the LoRaWAN network successfully. And DS03A-NB will send uplinks when:
  * Every 2 hours, this interval [[can be changed>>||anchor="H3.3.1A0SetTransmitIntervalTime"]].
  * There is an Open/Close event.  (This info can be disabled by AT+DISALARM=1)
@@ -612,7 +612,7 @@
  === 2.3.4  Historical Door Open/Close Event, FPORT~=3 ===
--DS03A-LB stores sensor values and users can retrieve these history values via the [[downlink command>>||anchor="H2.5DatalogFeature"]].
++DS03A-NB stores sensor values and users can retrieve these history values via the [[downlink command>>||anchor="H2.5DatalogFeature"]].
  The historical payload includes one or multiplies entries and every entry has the same payload as Real-Time open/close status.
@@ -640,7 +640,7 @@
  )))
  * (((
--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.
++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.
  )))
  For example, in the US915 band, the max payload for different DR is:
@@ -661,7 +661,7 @@
  **4. DR3**: total payload includes 22 entries of data.
  )))
--If DS03A-LB doesn't have any data in the polling time. It will uplink 11 bytes of 0
++If DS03A-NB doesn't have any data in the polling time. It will uplink 11 bytes of 0
  [[image:image-20230630155556-4.png||height="146" width="938"]]
@@ -741,161 +741,327 @@
  * (% style="color:#037691" %)**AT+INTMOD=3  **(%%)  ~/~/ Trigger by rising edge
--== 2.7 Alarm for continuously water flow ==
--(((
--This feature is to monitor and send Alarm for continuously water flow.
--)))
++== 2.7 Set Transmit Interval Time ==
--(((
--Example case is for Toilet water monitoring, if some one push toilet button, the toilet will have water flow. If the toilet button has broken and can't returned to original state, the water flow will keep for hours or days which cause huge waste for water.
--)))
  (((
--To monitor this faulty and send alarm, there are two settings:
++Feature: Change NB-IoT End Node Transmit Interval.
  )))
--* (((
--(% style="color:blue" %)**Stop Duration: Unit: Second**
--)))
--
  (((
--Default: 15s, If DS03A-NB didn't see any water flow in 15s, DS03A-NB will consider stop of water flow event.
++(% style="color:blue" %)**AT Command: AT+TDC**
  )))
--* (((
--(% style="color:blue" %)**Alarm Timer: Units: Minute; Default 0 minutes (means Alarm disable)**
++(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %)
++|=(% 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**
++|(% style="width:156px" %)AT+TDC=?|(% style="width:137px" %)Show current transmit Interval|(((
++30000
++OK
++the interval is 30000ms = 30s
  )))
--
--(((
--**Example:** 3 minutes, if DS03A-NB detect a start of water flow event and didn't detect a stop event within Alarm timer, DS03A-NB will send an Alarm to indicate a water flow abnormal alarm.
++|(% style="width:156px" %)AT+TDC=60000|(% style="width:137px" %)Set Transmit Interval|(((
++OK
++Set transmit interval to 60000ms = 60 seconds
  )))
  (((
--So for example, If we set stop duration=15s and Alarm Timer=3minutes. If the toilet water flow continuously for more than 3 minutes, Sensor will send an alarm (in Confirmed MODE) to platform.
++(% style="color:blue" %)**Downlink Command: 0x01**
  )))
  (((
--(% style="color:red" %)**Note:** **After this alarm is send, sensor will consider a stop of water flow and count for another new event. So if water flow waste last for 1 hour, Sensor will keep sending alarm every 3 minutes.**
++Format: Command Code (0x01) followed by 3 bytes time value.
  )))
  (((
--(% style="color:blue" %)**AT Command to configure:**
++If the downlink payload=0100003C, it means set the END Node's Transmit Interval to 0x00003C=60(S), while type code is 01.
  )))
  * (((
--AT+PTRIG=15,3   ~-~-> Set Stop duration: 15s, Alarm Timer: 3 minutes.
++Example 1: Downlink Payload: 0100001E       ~/~/ Set Transmit Interval (TDC) = 30 seconds
  )))
++* (((
++Example 2: Downlink Payload: 0100003C      ~/~/ Set Transmit Interval (TDC) = 60 seconds
++)))
++
++=== 3.3.3  Enable / Disable Alarm ===
++
++
++Feature: Enable/Disable Alarm for open/close event. Default value 0.
++
++(% style="color:blue" %)**AT Command: **
++
++(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:515px" %)
++|(% style="background-color:#d9e2f3; color:#0070c0; width:153px" %)**Command Example**|(% style="background-color:#d9e2f3; color:#0070c0; width:276px" %)**Function**|(% style="background-color:#d9e2f3; color:#0070c0; width:86px" %)**Response**
++|(% style="width:154px" %)AT+DISALARM=1|(% style="width:278px" %)End node will only send packets in TDC time.|OK
++|(% style="width:154px" %)AT+DISALARM=0|(% style="width:278px" %)End node will send packets in TDC time or status change for door sensor|OK
++
++(% style="color:blue" %)**Downlink Command: **
++
++0xA7 01     ~/~/ Same As AT+DISALARM=1
++
++0xA7 00     ~/~/ Same As AT+DISALARM=0
++
++
++=== 3.3.4  Alarm Base on Timeout ===
++
++
++DS03A-LB 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:
++
  * (((
--AT+ PTRIG=15,0  ~-~-> Default Value, disable water waste Alarm.
++(% style="color:blue" %)**Keep Status: Status to be monitor**
  )))
--(((
--(% style="color:blue" %)**Downlink Command to configure:**
++(% style="color:#037691" %)**Keep Status = 1**(%%): Monitor Close to Open event
++
++(% style="color:#037691" %)**Keep Status = 0**(%%): Monitor Open to Close event
++
++
++* (((
++(% style="color:blue" %)**Keep Time: Timeout to send an Alarm**
  )))
--(((
--Command: **0xAA aa bb cc**
++Range 0 ~~ 65535(0xFFFF) seconds.
++
++If (% style="color:#037691" %)**keep time = 0**(%%), Disable Alarm Base on Timeout feature.
++
++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.
++
++
++* (((
++(% style="color:blue" %)**Downlink Command**
  )))
--(((
--AA: Command Type Code
++(% style="color:#037691" %)**Command: 0xA9 aa bb cc dd**
++
++**A9:** Command Type Code
++
++**aa: **01:TTRIG1; 02:TTRIG2
++
++**bb:** status to be monitored
++
++**cc dd:** timeout.
++
++
++**1) AT+TTRIG1 : (PA8 of pin)**
++
++(% style="color:blue" %)**AT Command to configure:**
++
++* (((
++(% 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-LB 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.
++
++(% 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-LB 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.
  )))
--(((
--aa: Stop duration
++* (((
++(% style="color:#037691" %)**AT+TTRIG1=0,0**  (%%)  **~-~-> ** Default Value, disable timeout Alarm.
++
++
++
  )))
--(((
--bb cc: Alarm Timer
++(% style="color:blue" %)**Downlink Command to configure:**
++
++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.
++
++
++**2) AT+TTRIG2 : (PA4 of pin,need to use AT+TTRCHANNEL=2)**
++
++(% style="color:blue" %)**AT Command to configure:**
++
++* (((
++(% 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-LB 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.
++
++(% 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-LB 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.
  )))
--(((
--If user send 0xAA 0F 00 03: equal to AT+PTRIG=15,3
++* (((
++(% style="color:#037691" %)**AT+TTRIG2=0,0**  (%%)  **~-~-> ** Default Value, disable timeout Alarm.
++
++
++
  )))
++(% style="color:blue" %)**Downlink Command to configure:**
--== 2.8 Set the calculate flag ==
++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.
--Feature: Set the calculate flag
++=== 3.3.5  TTRIG1 & TTRIG2 timeout status alarm ===
--(% style="color:blue" %)**AT Command: AT+CALCFLAG**
--(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:461px" %)
--|=(% style="width: 158px;background-color:#4F81BD;color:white" %)**Command Example**|=(% style="width: 193px;background-color:#4F81BD;color:white" %)**Function**|=(% style="width: 110px;background-color:#4F81BD;color:white" %)**Response**
--|(% style="width:158px" %)AT+CALCFLAG =1|(% style="width:192px" %)Set the calculate flag to 1.|(% style="width:109px" %)OK
--|(% style="width:158px" %)AT+CALCFLAG =2|(% style="width:192px" %)Set the calculate flag to 2.|(% style="width:109px" %)OK
++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.
++(% style="color:blue" %)**AT Command:**
++
++(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %)
++|=(% style="width: 155px;background-color:#D9E2F3;color:#0070C0" %)**Command Example**|=(% style="width: 279px;background-color:#D9E2F3;color:#0070C0" %)**Function**|=(% style="width: 76px;background-color:#D9E2F3;color:#0070C0" %)**Response**
++|(% style="width:155px" %)(((
++AT+TTRALARM=0
++)))|(% style="width:279px" %)(((
++disable continuous alarm
++)))|(% style="width:84px" %)(((
++OK
++)))
++|(% style="width:155px" %)(((
++AT+TTRALARM=60
++)))|(% style="width:279px" %)(((
++The alarm interval is 60 minutes (unit: minutes)
++)))|(% style="width:84px" %)(((
++OK
++)))
++
  (% style="color:blue" %)**Downlink Command:**
--* **Example**: 0XA501         ~/~/  Same as AT+CALCFLAG =1
++Example:  0C aa  => AT+TTRALARM= aa
--== 2.9 Set count number ==
++=== 3.3.6  Count Mod ===
--Feature: Manually set the count number
--(% style="color:blue" %)**AT Command: AT+SETCNT**
++Feature: Manually set the count mode.
--(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:479px" %)
--|=(% style="width: 160px;background-color:#4F81BD;color:white" %)**Command Example**|=(% style="width: 223px;background-color:#4F81BD;color:white" %)**Function**|=(% style="width: 96px;background-color:#4F81BD;color:white" %)**Response**
--|(% style="width:160px" %)AT+ SETCNT =0|(% style="width:221px" %)Set the count number to 0.|(% style="width:95px" %)OK
--|(% style="width:160px" %)AT+ SETCNT =100|(% style="width:221px" %)Set the count number to 100.|(% style="width:95px" %)OK
++(% style="color:blue" %)**AT Command:**
++(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:515px" %)
++|=(% style="width: 154px;background-color:#D9E2F3;color:#0070C0" %)**Command Example**|=(% style="width: 275px;background-color:#D9E2F3;color:#0070C0" %)**Function**|=(% style="width: 86px;background-color:#D9E2F3;color:#0070C0" %)**Response**
++|(% style="width:155px" %)(((
++AT+COUNTMOD=0
++)))|(% style="width:277px" %)(((
++the count value keeps accumulating mode
++)))|(% style="width:86px" %)(((
++OK
++)))
++|(% style="width:155px" %)(((
++AT+COUNTMOD=1
++)))|(% style="width:277px" %)(((
++the count value will be reset after each TDC time(Last Close Duration Reset after each uplink)
++)))|(% style="width:86px" %)(((
++OK
++)))
++
  (% style="color:blue" %)**Downlink Command:**
--* **Example**: 0xA6000001      ~/~/  Same as AT+ SETCNT =1
++Example:  0B aa  => AT+COUNTMOD = second byte
--* **Example**: 0xA6000064      ~/~/  Same as AT+ SETCNT =100
--== 2.10 Set Transmit Interval Time ==
++=== 3.3.7  Number of channel of door sensors ===
--(((
--Feature: Change NB-IoT End Node Transmit Interval.
--)))
++Feature: Set the number of door sensor channels.
--(((
--(% style="color:blue" %)**AT Command: AT+TDC**
--)))
++(% style="color:blue" %)**AT Command:**
--(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %)
--|=(% 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**
--|(% style="width:156px" %)AT+TDC=?|(% style="width:137px" %)Show current transmit Interval|(((
--30000
++(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:500px" %)
++|=(% style="width: 155px;background-color:#D9E2F3;color:#0070C0" %)**Command Example**|=(% style="width: 288px; background-color:#D9E2F3;color:#0070C0" %)**Function**|=(% style="width: 57px;background-color:#D9E2F3;color:#0070C0" %)**Response**
++|(% style="width:155px" %)(((
++AT+TTRCHANNEL=1
++)))|(% style="width:259px" %)(((
++Set as single channel, only use PA8 pin as interrupt pin.
++)))|(% style="width:44px" %)(((
  OK
--the interval is 30000ms = 30s
  )))
--|(% style="width:156px" %)AT+TDC=60000|(% style="width:137px" %)Set Transmit Interval|(((
++|(% style="width:155px" %)(((
++AT+TTRCHANNEL=2
++)))|(% style="width:259px" %)(((
++Set as dual channel, use PA8 pin and PA4 pin as interrupt pin.
++)))|(% style="width:44px" %)(((
  OK
--Set transmit interval to 60000ms = 60 seconds
  )))
--(((
--(% style="color:blue" %)**Downlink Command: 0x01**
--)))
++(% style="color:blue" %)**Downlink Command:**
--(((
--Format: Command Code (0x01) followed by 3 bytes time value.
--)))
++Example:  0D aa => AT+TTRCHANNEL = second byte
--(((
--If the downlink payload=0100003C, it means set the END Node's Transmit Interval to 0x00003C=60(S), while type code is 01.
++
++=== 3.3.8  Set Time Sync Mode ===
++
++
++Feature: Enable/Disable Sync system time via LoRaWAN MAC Command (DeviceTimeReq), LoRaWAN server must support v1.0.3 protocol to reply to this command.
++
++SYNCMOD is set to 1 by default. If user wants to set a different time from the LoRaWAN server, the user needs to set this to 0.
++
++(% style="color:blue" %)**AT Command:**
++
++(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:500px" %)
++|=(% style="width: 155px;background-color:#D9E2F3;color:#0070C0" %)**Command Example**|=(% style="width: 288px; background-color:#D9E2F3;color:#0070C0" %)**Function**|=(% style="width: 57px;background-color:#D9E2F3;color:#0070C0" %)**Response**
++|(% style="width:155px" %)(((
++AT+SYNCMOD=1
++)))|(% style="width:259px" %)(((
++Enable Sync system time via LoRaWAN MAC Command (DeviceTimeReq) The default is zero time zone.
++)))|(% style="width:44px" %)(((
++OK
  )))
++|(% style="width:155px" %)(((
++AT+SYNCMOD=1,8
++)))|(% style="width:259px" %)(((
++Enable Sync system time via LoRaWAN MAC Command (DeviceTimeReq) Set to East eight time zone.
++)))|(% style="width:44px" %)(((
++OK
++)))
++|(% style="width:155px" %)AT+SYNCMOD=1,-12|(% style="width:259px" %)Enable Sync system time via LoRaWAN MAC Command (DeviceTimeReq) Set to West Twelve Time Zone.|(% style="width:44px" %)OK
--* (((
--Example 1: Downlink Payload: 0100001E       ~/~/ Set Transmit Interval (TDC) = 30 seconds
++(% style="color:blue" %)**Downlink Command:**
++
++0x28 01           ~/~/ Same As AT+SYNCMOD=1
++
++0x28 01 08      ~/~/ Same As AT+SYNCMOD=1,8
++
++0x28 01 F4      ~/~/ Same As AT+SYNCMOD=1,-12
++
++0x28 00           ~/~/ Same As AT+SYNCMOD=0
++
++
++=== 3.3.9  Clear the open door times and the duration of the last open door ===
++
++
++(% style="color:blue" %)**AT Command:**
++
++(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %)
++|=(% style="width: 163px;background-color:#D9E2F3;color:#0070C0" %)**Command Example**|=(% style="width: 290px; background-color:#D9E2F3;color:#0070C0" %)**Function**|=(% style="width: 57px;background-color:#D9E2F3;color:#0070C0" %)**Response**
++|(% style="width:155px" %)AT+CLRC|(% style="width:259px" %)clear the open door times and the duration of the last open door.|(% style="width:44px" %)(((
++OK
  )))
--* (((
--Example 2: Downlink Payload: 0100003C      ~/~/ Set Transmit Interval (TDC) = 60 seconds
++(% style="color:blue" %)**Downlink Command:**(%%)0xA6 01
--
++The sensor will clear the open door times and the duration of the last open door.
++
++
++=== 3.3.10  Set the count value of the number of open door ===
++
++
++(% style="color:blue" %)**AT Command:**
++
++(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:500px" %)
++|=(% style="width: 155px;background-color:#D9E2F3;color:#0070C0" %)**Command Example**|=(% style="width: 288px; background-color:#D9E2F3;color:#0070C0" %)**Function**|=(% style="width: 57px;background-color:#D9E2F3;color:#0070C0" %)**Response**
++|(% style="width:155px" %)(((
++AT+SETCNT=1,100
++)))|(% style="width:259px" %)(((
++Set the open door times of PA8 pin to 100 times.
++)))|(% style="width:44px" %)(((
++OK
  )))
++|(% style="width:155px" %)AT+SETCNT=1,0|(% style="width:259px" %)Clear the open door times of PA8 pin.|(% style="width:44px" %)OK
++|(% style="width:155px" %)(((
++AT+SETCNT=2,50
++)))|(% style="width:259px" %)(((
++Set the open door times of PA4 pin to 100 times.
++)))|(% style="width:44px" %)(((
++OK
++)))
++(% style="color:blue" %)**Downlink Command:**
++
++0xA6 01 00 00 64    ==>   AT+SETCNT=1,100
++
++0xA6 01 00 00 00    ==>   AT+SETCNT=1,0
++
++0xA6 02 00 00 32    ==>   AT+SETCNT=2,50
++
++
  = 3. Configure DS03A-NB =
  == 3.1 Configure Methods ==

Changes for page wiki_test

Summary

Details

Applications

Navigation