image-20231011093014-5.png

Table of Contents:

1. Introduction

1.1 What is DS03A-NB NB-IoT Door Sensor

The Dragino DS03A-NB is a  NB-IoT Door Sensor for Internet of Things solution. It 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.

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-NB supports Datalog Feature, it can save the data when there is no NB-IoT network and uplink when network recover.

DS03A-NB has the 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 is designed for outdoor use. It has a weatherproof enclosure and industrial level battery to work in low to high temperatures

DS03A-NB supports different uplink methods including MQTT, MQTTs, UDP & TCP for different application requirement, and support uplinks to various IoT Servers.

DS03A-NB supports BLE configure and OTA update which make user easy to use.

DS03A-NB is powered by 8500mAh Li-SOCI2 battery, it is designed for long-term use up to several years.

DS03A-NB has optional built-in SIM card and default IoT server connection version. Which makes it works with simple configuration.

image-20231011093807-6.png

1.2 ​Features

  • NB-IoT Bands: B1/B2/B3/B4/B5/B8/B12/B13/B17/B18/B19/B20/B25/B28/B66/B70/B85 @H-FDD
  • Ultra-low power consumption
  • Door Open/Close detect
  • Door open/close statistics
  • Datalog Feature
  • Open Alarm Feature
  • Multiply Sampling and one uplink
  • Support Bluetooth v5.1 remote configure and update firmware
  • Uplink on periodically
  • Downlink to change configure
  • 8500mAh Battery for long term use
  • Nano SIM card slot for NB-IoT SIM
      

1.3 Specification

Common DC Characteristics:

  • Supply Voltage: 2.5v ~ 3.6v
  • Operating Temperature: -40 ~ 85°C

NB-IoT Spec:

NB-IoT Module: BC660K-GL

Support Bands:

  • B1 @H-FDD: 2100MHz
  • B2 @H-FDD: 1900MHz
  • B3 @H-FDD: 1800MHz
  • B4 @H-FDD: 2100MHz
  • B5 @H-FDD: 860MHz
  • B8 @H-FDD: 900MHz
  • B12 @H-FDD: 720MHz
  • B13 @H-FDD: 740MHz
  • B17 @H-FDD: 730MHz
  • B18 @H-FDD: 870MHz
  • B19 @H-FDD: 870MHz
  • B20 @H-FDD: 790MHz
  • B25 @H-FDD: 1900MHz
  • B28 @H-FDD: 750MHz
  • B66 @H-FDD: 2000MHz
  • B70 @H-FDD: 2000MHz
  • B85 @H-FDD: 700MHz

Battery:

  • Li/SOCI2 un-chargeable battery
  • Capacity: 8500mAh
  • Self Discharge: <1% / Year @ 25°C
  • Max continuously current: 130mA
  • Max boost current: 2A, 1 second

Power Consumption

  • STOP Mode: 10uA @ 3.3v
  • Max transmit power: 350mA@3.3v
      

1.4 Applications

1654741400370-813.png

1.5 Sleep mode and working mode

Deep Sleep Mode: Sensor doesn't have any NB-IoT activate. This mode is used for storage and shipping to save battery life.

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.

1.6 Button & LEDs

1675071855856-879.png

Behavior on ACTFunctionAction
Pressing ACT between 1s < time < 3sSend an uplink

If sensor has already attached to NB-IoT network, sensor will send an uplink packet, blue led will blink once.
Meanwhile, BLE module will be active and user can connect via BLE to configure device.

Pressing ACT for more than 3sActive Device

Green led will fast blink 5 times, device will enter OTA mode for 3 seconds. And then start to  attach NB-IoT network.
Green led will solidly turn on for 5 seconds after joined in network.
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.

Fast press ACT 5 times.Deactivate DeviceRed led will solid on for 5 seconds. Means device is in Deep Sleep Mode.

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.

1.7 BLE connection

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:

  • Press button to send an uplink
  • Press button to active device.
  • Device Power on or reset.

If there is no activity connection on BLE in 60 seconds, sensor will shut down BLE module to enter low power mode.

1.8 Pin Definitions , Switch & SIM Direction

image-20230819104805-5.png

1.8.1 Jumper JP2

Power on Device when put this jumper.

1.8.2 BOOT MODE / SW1

1) 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.

2) Flash: work mode, device starts to work and send out console output for further debug

1.8.3 Reset Button

Press to reboot the device.

 

1.8.4 SIM Card Direction

See this link. How to insert SIM Card.

1.9 Mechanical

1675143884058-338.png

1675143899218-599.png

1675143909447-639.png

Probe Mechanical:

1654741444887-479.png

1.10 Magnet Distance

  • Wood Door: 10mm ~ 30mm
  • Iron Door: 30 ~ 45mm
      

2. Use DS03A-NB to communicate with IoT Server

2.1 Send data to IoT server via NB-IoT network

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:

image-20231011093807-6.png

There are two version: -GE and -1D version of DS03A-NB.

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.

Below shows result of different server as a glance.

ServersDash BoardComments
Node-Red

image-20230819113244-8.png

 
DataCake

image-20230819113244-9.png

 
Tago.IO  
General UDPRaw Payload. Need Developer to design Dash Board 
General MQTTRaw Payload. Need Developer to design Dash Board 
ThingSpeak

image-20230819113244-10.png

 
ThingsBoard

image-20230819113244-11.png

 

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.

2.2 ​Payload Types

To meet different server requirement, DS03A-NB supports different payload type.

Includes:

User can specify the payload type when choose the connection protocol. Example:

AT+PRO=2,0            // Use UDP Connection & hex Payload

AT+PRO=2,5            // Use UDP Connection & Json Payload

AT+PRO=3,5            // Use MQTT Connection & Json Payload

2.2.1 General Json Format(Type=5)

This is the General Json Format. Payloads in General Json format for single-channel mode and double-channel mode have different byte lengths.

The General Json format payload for the single-channel mode is as follows:

{"IMEI":"863663062798914","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.34,"signal":17,"1":[1,0,0,"2024/06/11 03:09:07"],"2":[1,0,0,"2024/06/11 02:51:00"],"3":[1,0,0,"2024/06/11 02:36:00"],"4":[8,100,100,"2024/05/30 10:19:53"],"5":[8,100,100,"2024/05/30 10:19:18"],"6":[8,100,100,"2024/05/30 10:17:53"],"7":[8,100,100,"2024/05/30 10:16:53"],"8":[8,100,100,"2024/05/30 10:16:28"]}

image-20240611150437-1.png

The General Json format payload for the double-channel mode is as follows:

{"IMEI":"863663062798914","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.34,"signal":15,"1":[1,0,0,1,0,0,"2024/06/11 05:49:07"],"2":[0,200,300,1,0,0,"2024/06/11 05:34:07"],"3":[0,200,300,1,0,0,"2024/06/11 05:19:07"],"4":[0,200,300,1,0,0,"2024/06/11 05:04:07"],"5":[0,200,300,1,0,0,"2024/06/11 04:49:07"],"6":[0,200,300,1,0,0,"2024/06/11 04:34:07"],"7":[0,200,300,1,0,0,"2024/06/11 04:19:07"],"8":[0,200,300,1,0,0,"2024/06/11 04:04:07"]}

image-20240611150520-2.png

Notice, from above payload:

  • 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.
  • Json entry 1 ~ 8 are the last 1 ~ 8 sampling data as specify by AT+CLOCKLOG=1,65535,15,8  Command. Each entry includes (from left to right):

          Single-channel mode: level status, door open num, last open time, Sampling time. 

          Double-channel mode: level status, door open num, last open time, level status2, door open sum2, last open time2, Sampling time. 

2.2.2 HEX format Payload(Type=0)

This is the HEX Format. Payloads in HEX format for single-channel mode and double-channel mode have different byte lengths.

The HEX format payload for the single-channel mode is as follows:

062798914127b0d00120101000000000000006667e2e0010000000000006667e1cf010000000000006667de4b010000000000006667dac7010000000000006667d743010000000000006667d3bf010000000000006667d03b010000000000006667ccb7010000000000006667c7c7

image-20240611151016-5.png

If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data.

image-20240611151101-6.png

The HEX format payload for the double-channel mode is as follows:

062798914127b0cea0e01010000000000000001000000000000006667e66a01000000000000010000000000006667e55301000000000000000000c800012c6667e1cf01000000000000000000c800012c6667de4b01000000000000000000c800012c6667dac701000000000000000000c800012c6667d74301000000000000000000c800012c6667d3bf01000000000000000000c800012c6667d03b01000000000000000000c800012c6667ccb7

image-20240611151148-7.png

If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data.

image-20240611151206-8.png

Version:

These bytes include the hardware and software version.

Higher byte: Specify Sensor Model: 0x12 for DS03A-NB

Lower byte: Specify the software version: 0x7b=123, means firmware version 1.2.3

BAT (Battery Info):

Ex1: 0x0dda = 3546mV

Signal Strength:

NB-IoT Network signal Strength.

Ex1: 0x15 = 21

0        -113dBm or less

1        -111dBm

2...30 -109dBm... -53dBm

31      -51dBm or greater

99      Not known or not detectable

Timestamp:   

Unit Timestamp Example: 650abc40(H) = 1695202368(D)

Put the decimal value into this link(https://www.epochconverter.com)) to get the time.

2.2.3 ThingsBoard Payload(Type=3)

Type3 payload special design for ThingsBoard, it will also configure other default server to ThingsBoard.

The type3 format payload for the single-channel mode is as follows:

{
    "topic": "2276492",
    "payload": {
        "IMEI": "863663062798914",
        "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.33,
        "signal": 22,
        "1": [1, 0, 0, "2024/06/11 06:08:46"],
        "2": [1, 0, 0, "2024/06/11 05:49:07"],
        "3": [1, 0, 0, "2024/06/11 05:34:07"],
        "4": [1, 0, 0, "2024/06/11 05:19:07"],
        "5": [1, 0, 0, "2024/06/11 05:04:07"],
        "6": [1, 0, 0, "2024/06/11 04:49:07"],
        "7": [1, 0, 0, "2024/06/11 04:34:07"],
        "8": [1, 0, 0, "2024/06/11 04:19:07"]
    }
}

image-20240611151445-9.png

The type3 format payload for the double-channel mode is as follows:

{
    "topic": "2276492",
    "payload": {
        "IMEI": "863663062798914",
        "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.34,
        "signal": 20,
        "1": [1, 0, 0, 1, 0, 0, "2024/06/11 06:08:46"],
        "2": [1, 0, 0, 1, 0, 0, "2024/06/11 05:49:07"],
        "3": [0, 200, 300, 1, 0, 0, "2024/06/11 05:34:07"],
        "4": [0, 200, 300, 1, 0, 0, "2024/06/11 05:19:07"],
        "5": [0, 200, 300, 1, 0, 0, "2024/06/11 05:04:07"],
        "6": [0, 200, 300, 1, 0, 0, "2024/06/11 04:49:07"],
        "7": [0, 200, 300, 1, 0, 0, "2024/06/11 04:34:07"],
        "8": [0, 200, 300, 1, 0, 0, "2024/06/11 04:19:07"]
    }
}

image-20240611151543-10.png

2.2.4 ThingSpeak Payload(Type=1)

This payload meets ThingSpeak platform requirement. It includes eight fields. Form 1~8 are:

Distance, Battery & Signal. This payload type only valid for ThingsSpeak Platform

As below:

field1=Flow value&field2=Battery value&field3=signal value

image-20231115154757-2.png

image-20231115154821-3.png

2.3 Test Uplink and Change Update Interval

By default, Sensor will send uplinks every 2 hours & AT+NOUD=8

User can use below commands to change the uplink interval.

AT+TDC=600        // Set Update Interval to 600s

User can also push the button for more than 1 seconds to activate an uplink.

Notice: The AT+NOUD feature is upgraded to Clock Logging, please refer Clock Logging Feature.

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:

  • 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)
  • AT+NOUD=8     //  The device uploads 8 sets of recorded data by default. Up to 32 sets of record data can be uploaded.

The diagram below explains the relationship between TR, NOUD, and TDC more clearly:

1692424376354-959.png

2.5 Trggier an uplink by external interrupt

DS03A-NB has an external trigger interrupt function. Users can use the PB15 pin to trigger the upload of data packets.

AT command:

  • AT+INTMOD         // Set the trigger interrupt mode
  • AT+INTMOD=0    // Disable Interrupt
  • AT+INTMOD=1    // Trigger by rising and falling edge
  • AT+INTMOD=2    // Trigger by falling edge
  • AT+INTMOD=3    // Trigger by rising edge
      

2.6 Set Transmit Interval Time

Feature: Change NB-IoT End Node Transmit Interval.

AT Command: AT+TDC

Command ExampleFunctionResponse
AT+TDC=?Show current transmit Interval

30000
OK
the interval is 30000ms = 30s

AT+TDC=60000Set Transmit Interval

OK
Set transmit interval to 60000ms = 60 seconds

Downlink Command: 0x01

Format: Command Code (0x01) followed by 3 bytes time value.

If the downlink payload=0100003C, it means set the END Node's Transmit Interval to 0x00003C=60(S), while type code is 01.

  • Example 1: Downlink Payload: 0100001E       // Set Transmit Interval (TDC) = 30 seconds

  • Example 2: Downlink Payload: 0100003C      // Set Transmit Interval (TDC) = 60 seconds 

      

2.7 Enable / Disable Alarm

Feature: Enable/Disable Alarm for open/close event. Default value 0.

AT Command: 

Command ExampleFunctionResponse
AT+DISALARM=1End node will only send packets in TDC time.OK
AT+DISALARM=0End node will send packets in TDC time or status change for door sensorOK

Downlink Command: 

0xA7 01     // Same As AT+DISALARM=1

0xA7 00     // Same As AT+DISALARM=0

2.8 Alarm Base on Timeout

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:

  • Keep Status: Status to be monitor

Keep Status = 1: Monitor Close to Open event

Keep Status = 0: Monitor Open to Close event

  • Keep Time: Timeout to send an Alarm

Range 0 ~ 65535(0xFFFF) seconds.

If keep time = 0, Disable Alarm Base on Timeout feature.

If keep time > 0, device will monitor the keep status event and send an alarm when status doesn't change after timeout.

  • Downlink Command

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)

AT Command to configure:

  • 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 1st byte of payload) on this uplink packet is set to 1.

    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 1st byte of payload) on this uplink packet is set to 1.

  • AT+TTRIG1=0,0    -->  Default Value, disable timeout Alarm.

     

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)

AT Command to configure:

  • 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 12st byte of payload) on this uplink packet is set to 1.

    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 12st byte of payload) on this uplink packet is set to 1.

  • AT+TTRIG2=0,0    -->  Default Value, disable timeout Alarm.

     

Downlink Command to configure:

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. 

2.9 TTRIG1 & TTRIG2 timeout status alarm

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.

AT Command:

Command ExampleFunctionResponse

AT+TTRALARM=0

disable continuous alarm

OK

AT+TTRALARM=60

The alarm interval is 60 minutes (unit: minutes)

OK

Downlink Command:

Example:  0C aa  => AT+TTRALARM= aa

2.10 Count Mod

Feature: Manually set the count mode.

AT Command:

Command ExampleFunctionResponse

AT+COUNTMOD=0

the count value keeps accumulating mode

OK

AT+COUNTMOD=1

the count value will be reset after each TDC time(Last Close Duration Reset after each uplink)

OK

Downlink Command:

Example:  0B aa  => AT+COUNTMOD = second byte

2.11 Number of channel of door sensors

Feature: Set the number of door sensor channels.

AT Command:

Command ExampleFunctionResponse

AT+TTRCHANNEL=1

Set as single channel, only use PA8 pin as interrupt pin.

OK

AT+TTRCHANNEL=2

Set as dual channel, use PA8 pin and PA4 pin as interrupt pin.

OK

Downlink Command:

Example:  0D aa => AT+TTRCHANNEL = second byte

2.12 Clear the open door times and the duration of the last open door

AT Command:

Command ExampleFunctionResponse
AT+CLRCclear the open door times and the duration of the last open door.

OK

Downlink Command:0xA6 01

The sensor will clear the open door times and the duration of the last open door.

2.13 Set the count value of the number of open door

AT Command:

Command ExampleFunctionResponse

AT+SETCNT=1,100

Set the open door times of PA8 pin to 100 times.

OK

AT+SETCNT=1,0Clear the open door times of PA8 pin.OK

AT+SETCNT=2,50

Set the open door times of PA4 pin to 100 times.

OK

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

2.14 Clock logging (Since firmware version v1.2.1)

Sometimes when we deploy lots of end nodes in field. We want all sensors sample data at the same time, and upload these data together for analyze. In such case, we can use clock loging feature.

We can use this command to set the start time of data recording and the time interval to meet the requirements of the specific collection time of data.

  • AT Command: AT+CLOCKLOG=a,b,c,d

a: 0: Disable Clock logging.   1: Enable Clock Logging

b: Specify First sampling start second: range (0 ~ 3599, 65535)         // Note: If parameter b is set to 65535, the log period starts after the node accesses the network and sends packets.

c: Specify the sampling interval: range (0 ~ 255 minutes)

d: How many entries should be uplink on every TDC (max 32)

image-20240315141254-1.png

Example:

AT+CLOCKLOG=1,65535,1,5

After the node sends the first packet, data is recorded to the memory at intervals of 1 minute. For each TDC uplink, the uplink load will include: battery information + the last 5 memory records (payload + timestamp).

image-20240316150911-1.png

Note: Users need to synchronize the server time before configuring this command. If the server time is not synchronized before this command is configured, the command takes effect only after the node is reset.

  • Downlink Command: 0x0A

Format: Command Code (0x0A) followed by 5 bytes.

  • Example 1: Downlink Payload: 0A01FFFF0F08             // Set SHT record time: AT+CLOCKLOG=1,65535,15,8
  • Example 1: Downlink Payload: 0A0104B00F08             // Set SHT record time: AT+CLOCKLOG=1,1200,15,8

Note: When entering the downlink payload, there must be no Spaces between bytes.

2.15 Example Query saved historical records

  • AT Command: AT+CDP

This command can be used to search the saved history, recording up to 32 groups of data, each group of historical data contains a maximum of 100 bytes.

image-20240316151014-2.png

2.16 Uplink log query

  • AT Command: AT+GETLOG

This command can be used to query upstream logs of data packets.

image-20240407191922-2.png

2.17 Scheduled domain name resolution

This command is used to set up scheduled domain name resolution.

AT command:

  • AT+DNSTIMER=XX   // Unit: hour

After setting this command, domain name resolution will be performed regularly.

2.18 Set the QoS level

This command is used to set the QoS level of MQTT.

AT command:

  • AT+MQOS=xx    // 0~2

Downlink Command: 0x07

Format: Command Code (0x07) followed by 1 byte.

Ex1: Downlink payload: 0x0700   //AT+MQOS=0

Ex2: Downlink payload: 0x0701   //AT+MQOS=1

3. Configure DS03A-NB

3.1 Configure Methods

DS03A-NB supports below configure method:

3.2 AT Commands Set

AT+<CMD>?           : Help on <CMD>

AT+<CMD>                      : Run <CMD>

AT+<CMD>=<value>      : Set the value

AT+<CMD>=?          : Get the value

General Commands       

AT                    : Attention        

AT?                  : Short Help      

ATZ                 : MCU Reset     

AT+TDC          : Application Data Transmission Interval

AT+CFG          : Print all configurations

AT+CFGMOD           : Working mode selection

AT+DEUI                  : Get or set the Device ID

AT+INTMOD            : Set the trigger interrupt mode

AT+5VT           : Set extend the time of 5V power   

AT+PRO          : Choose agreement

AT+RXDL        : Extend the sending and receiving time

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+SHTEMP:   Get or Set alarm of temp

AT+SHHUM:   Get or Set alarm of moisture

AT+SERVADDR :   Server Address

MQTT Management

AT+CLIENT               : Get or Set MQTT client

AT+UNAME              : Get or Set MQTT Username

AT+PWD                  : Get or Set MQTT password

AT+PUBTOPIC          : Get or Set MQTT publish topic

AT+SUBTOPIC          : Get or Set MQTT subscription topic

Information           

AT+FDR              : Factory Data Reset

AT+PWORD        : Serial Access Password

AT+LDATA           : Get the last upload data

AT+CDP               : Read or Clear cached data

4. Battery & Power Consumption

DS03A-NB use ER26500 + SPC1520 battery pack. See below link for detail information about the battery info and how to replace.

Battery Info & Power Consumption Analyze .

5. Firmware update

User can change device firmware to::

  • Update with new features.
  • Fix bugs. 

Firmware and changelog can be downloaded from : Firmware download link

Methods to Update Firmware:

  • (Recommended way) OTA firmware update via BLE: Instruction.

6. FAQ

6.1 How can I access the BC660K-GL AT Commands?

User can access to BC660K-GL directly and send AT Commands.

See BC660K-GL AT Command set

6.2 How to configure the certificate?

User can can refer to this description to configure the certificate.

7. Order Info

Part Number: DS03A-NB-XX

XX

  • GE: General version ( Exclude SIM card)
  • 1D: with 1NCE* 10 years 500MB SIM card and Pre-configure to DataCake server

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

8. ​Packing Info

Package Includes:

  • DS03A-NB NB-IoT Door sensor x 1
  • External antenna x 1

Dimension and weight:

  • Device Size: 13.0 x 5 x 4.5 cm
  • Device Weight: 150g
  • Package Size / pcs : 14.0 x 8x 5 cm
  • Weight / pcs : 180g
      

9. Support

  • 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.cc.

   

Tags:
    
Copyright ©2010-2022 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0