TS01-NB -- NB-IoT Tilting Sensor User Manual
Table of Contents:
- 1. Introduction
- 2. Use TS01-NB to communicate with IoT Server
- 2.1 Send data to IoT server via NB-IoT network
- 2.2 Payload Types
- 2.3 Angle Alarm Feature
- 2.4 Calibration and installation direction
- 2.5 Test Uplink and Change Update Interval
- 2.6 Multi-Samplings and One uplink
- 2.7 Trggier an uplink by external interrupt
- 2.8 Set Calibration
- 2.9 Set installation direction
- 2.10 Set angle alarm
- 2.11 Set alarm mode
- 2.12 Clock logging (Since firmware version v1.2.1)
- 2.13 Example Query saved historical records
- 2.14 Uplink log query
- 2.15 Scheduled domain name resolution
- 2.16 Set the QoS level
- 2.17 Set the downlink debugging mode(Since firmware v1.3.0)
- 2.18 Domain name resolution settings(Since firmware v1.3.0)
- 3. Configure TS01-NB
- 4. Battery & Power Consumption
- 5. Firmware update
- 6. FAQ
- 7. Order Info
- 8. Packing Info
- 9. Support
1. Introduction
1.1 What is NB-IoT Tilting Sensor
The Dragino TS01-NB is a NB-IoT Tilting Sensor for Internet of Things solution. TS01-NB is an outdoor Tilting Sensor specially designed for detecting the angle of trees, buildings or large scale equipment.
TS01-NB measures pitch and roll angle and converts to NB-IoT wireless data and sends to IoT platform via NB-IoT network.
TS01-NB supports different uplink methods including MQTT, MQTTs, UDP & TCP for different application requirement, and support uplinks to various IoT Servers.
TS01-NB supports BLE configure and OTA update which make user easy to use.
TS01-NB is powered by 8500mAh Li-SOCI2 battery, it is designed for long-term use up to several years.
TS01-NB has optional built-in SIM card and default IoT server connection version. Which makes it works with simple configuration.
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
- Detect pitch and roll angle
- Support Angle Alarm
- Support Datalog feature
- Multiply Sampling and one uplink
- Support BLE remote configure and update firmware
- Uplink on periodically
- Downlink to change configure
- 8500mAh Battery for long term use
- Uplink via MQTT, MQTTs, TCP, or UDP
- 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
Angle Spec:
- Measure Pitch and Roll
- Accuracy: 0.3°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 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.5 Button & LEDs
Behavior on ACT | Function | Action |
---|---|---|
Pressing ACT between 1s < time < 3s | Send an uplink | If sensor has already attached to NB-IoT network, sensor will send an uplink packet, blue led will blink once. |
Pressing ACT for more than 3s | Active Device | Green led will fast blink 5 times, device will enter OTA mode for 3 seconds. And then start to attach NB-IoT network. |
Fast press ACT 5 times. | Deactivate Device | Red 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.6 BLE connection
TS01-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.7 Pin Definitions , Switch & SIM Direction
TS01-NB use the mother board which as below.
1.7.1 Jumper JP2
Power on Device when put this jumper.
1.7.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.7.3 Reset Button
Press to reboot the device.
1.7.4 SIM Card Direction
See this link. How to insert SIM Card.
1.8 Sketch of Pitch and Roll
1.9 Installation direction
Horizontal installation:
Vertical installation:
2. Use TS01-NB to communicate with IoT Server
2.1 Send data to IoT server via NB-IoT network
The TS01-NB is equipped with a NB-IoT module, the pre-loaded firmware in TS01-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 TS01-NB.
Below shows the network structure:
There are two version: -GE and -1D version of TS01-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 TS01-NB send data to IoT server.
- Install NB-IoT SIM card and configure APN. See instruction of Attach Network.
- Set up sensor to point to IoT Server. See instruction of Configure to Connect Different Servers.
Below shows result of different server as a glance.
Servers | Dash Board | Comments |
Node-Red | ||
DataCake | ||
Tago.IO | ||
General UDP | Raw Payload. Need Developer to design Dash Board | |
General MQTT | Raw Payload. Need Developer to design Dash Board | |
ThingSpeak | ||
ThingsBoard |
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 TS01-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, TS01-NB supports different payload type.
Includes:
- General JSON format payload. (Type=5)
- HEX format Payload. (Type=0)
- ThingSpeak Format. (Type=1)
- ThingsBoard Format. (Type=3)
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,0 // Use MQTT Connection & hex Payload
AT+PRO=3,1 // Use MQTT Connection & ThingSpeak
AT+PRO=3,3 // Use MQTT Connection & ThingsBoard
AT+PRO=3,5 // Use MQTT Connection & Json Payload
AT+PRO=4,0 // Use TCP Connection & hex Payload
AT+PRO=4,5 // Use TCP Connection & Json Payload
2.2.1 General Json Format(Type=5)
This is the General Json Format. As below:
{"IMEI":"863663062798914","IMSI":"460083513507314","Model":"TS01-NB","temperature":25.6,"roll":0.00,"pitch":0.00,"interrupt":0,"interrupt_level":0,"battery":3.21,"signal":17,"time":"2024/11/21 05:53:38","1":[-409.5,13.23,0.00,"2024/11/21 05:26:12"],"2":[-409.5,13.27,0.00,"2024/11/21 05:11:12"],"3":[-409.5,13.41,0.00,"2024/11/21 04:56:12"],"4":[-409.5,13.26,0.00,"2024/11/21 04:41:12"],"5":[-409.5,13.29,0.00,"2024/11/21 04:26:12"],"6":[-409.5,13.85,0.00,"2024/11/21 04:11:12"],"7":[-409.5,7.14,0.00,"2024/11/21 03:10:21"],"8":[22.7,7.14,0.00,"2024/11/21 01:22:43"]}
Notice, from above payload:
- Temperature, Roll, Pitch, Interrupt, Interrupt_level, Battery, Signal & time 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): Temperature, Roll, Pitch, Sampling time.
2.2.2 HEX format Payload(Type=0)
This is the HEX Format. As below:
f863663062798914f46008351350731402820c9f0f000000000000f9000c01ff673ecc53f00109690000673ec474f001096f0000673ec0f0f001098a0000673ebd6cf001096d0000673eb9e8f00109740000673eb664f00109d90000673eb2e0f00105140000673ea49d00e305140000673e8b63
Version:
These bytes include the hardware and software version.
Higher byte: Specify Sensor Model: 0x02 for TS01-NB
Lower byte: Specify the software version: 0x82=130, means firmware version 1.3.0
BAT (Battery Info):
Sensor Battery Level.
Ex1: 0x0B45 = 2885mV
Ex2: 0x0B49 = 2889mV
Direction:
Read:0x(00)=0 // horizontal direction
Read:0x(01)=1 // Vertical direction
Level of PA4:
payload: 0x00 --> The PA4 is low level.
payload: 0x01 --> The PA4 is high level.
Interrupt:
This data field shows if this packet is generated by interrupt or not.
Example:
If byte[0]&0x01=0x00 : Normal uplink packet.
If byte[0]&0x01=0x01 : Interrupt Uplink Packet.
Interrupt_level:
This byte shows whether the interrupt is triggered by a high or low level.
Ex1: 0x00 Interrupt triggered by falling edge (low level)
Ex2: 0x01 Interrupt triggered by rising edge (high level)
DS18B20 Temperature:
Example:
If payload is: 0105H: (0105 & 8000 == 0), temp = 0105H /10 = 26.1 degree
If payload is: FF3FH : (FF3F & 8000 == 1) , temp = (FF3FH - 65536)/10 = -19.3 degrees.
(FF3F & 8000:Judge whether the highest bit is 1, when the highest bit is 1, it is negative)
Roll:
Read: 0x(019C)=412 Value: 412 / 100=4.12
Pitch:
Read: 0x(0251)=593 Value: 593/ 100=5.93
TimeStamp:
Unit TimeStamp Example: 64e2d74f(H) = 1692587855(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.
{
"topic": "2276492",
"payload": {
"IMEI": "863663062798914",
"Model": "TS01-NB",
"temperature": 25.4,
"roll": 106.85,
"pitch": 3.39,
"interrupt": 0,
"interrupt_level": 0,
"battery": 3.34,
"signal": 16,
"1": [25.4, 106.8, 3.41, "2024/05/29 06:57:59"],
"2": [25.4, 106.83, 3.41, "2024/05/29 06:57:47"],
"3": [25.5, -0.75, -0.82, "2024/05/29 06:56:26"],
"4": [25.5, -0.75, -0.81, "2024/05/29 06:54:59"],
"5": [25.5, -0.73, -0.82, "2024/05/29 06:53:59"],
"6": [25.5, -0.77, -0.81, "2024/05/29 06:51:45"],
"7": [25.6, -0.76, -0.81, "2024/05/29 06:50:44"],
"8": [25.6, -0.75, -0.81, "2024/05/29 06:49:44"]
}
}
2.2.4 ThingSpeak Payload(Type=1)
This payload meets ThingSpeak platform requirement. It includes only five fields. Form 1~5 are:
Temperature, Roll, Pitch, Battery & Signal. This payload type only valid for ThingsSpeak Platform
As below:
field1=Temperature value&field2=Roll value&field3=Pitch value&field4=Battery value&field5=Signal value
2.3 Angle Alarm Feature
TS01-NB work flow with Alarm feature.
TS01-NB has two alarm modes.
Alarm Mode 1:
AT+AMOD=1
AT+XALARM=Xvalue, AT+YALARM=Yvalue
When an angle change is detected that exceeds the range compared to the last time, an alarm is reported.
For example:
AT+XALARM=10
AT+YALARM=20
The last angle measured on the X-axis was 120 degrees, and this time the angle measured on the X-axis is 135 degrees, an alarm will be triggered to upload a data packet.
The last time the angle measured on the Y-axis was 100 degrees, but this time the angle measured on the Y-axis is 50 degrees, which will trigger an alarm and upload the data packet.
If the alarm conditions are met on the X-axis or Y-axis, an alarm will be triggered.
Alarm Mode 2:
AT+AMOD=2
AT+XALARM=min,max
When min=0, and max≠0, Alarm higher than max
When min≠0, and max=0, Alarm lower than min
When min≠0 and max≠0, Alarm higher than max or lower than min
Example:
AT+ XALARM=50,80 // Alarm when Roll lower than 50.
AT+YALARM=min,max
When min=0, and max≠0, Alarm higher than max
When min≠0, and max=0, Alarm lower than min
When min≠0 and max≠0, Alarm higher than max or lower than min
Example:
AT+ YALARM=20,30 // Alarm when Pitch lower than 20.
Alarm Mode 0:
AT+AMOD=0 // Turn off alarm function
Alarm time setting:
AT+TR=180 // It means triggering an alarm every 3 minutes.
Since firmware version v1.2.1,AT+TR is overridden by the clock recording function, The alarm interval is consistent with the detection interval of the clock recording function.
AT+CLOCKLOG=1,65535,15,8 // It means triggering an alarm every 15 minutes.
2.4 Calibration and installation direction
AT+CAL : Calibration angle
NOTE: If the installation direction is horizontal, the user needs to place the device horizontally for calibration. If the installation direction is vertical, the user needs to place the device vertically for calibration. If the direction is incorrect, it may result in opposite angles or inaccurate degrees.
When the calibration angle is 0 or close to 0, it is considered successful calibration.
Installation direction command:
AT+INSTAL=0 // horizontal direction
AT+INSTAL=1 // Vertical direction
2.5 Test Uplink and Change Update Interval
By default, Sensor will send uplinks every 2 hours
User can use below commands to change the uplink interval.
AT+TDC=7200 // Set Update Interval to 7200s
User can also push the button for more than 1 seconds to activate an uplink.
2.6 Multi-Samplings and One uplink
Notice: The AT+NOUD feature is upgraded to Clock Logging, please refer Clock Logging Feature.
To save battery life, TS01-NB will sample Idc_input & Vdc_input 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:
2.7 Trggier an uplink by external interrupt
TS01-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,as a digital input pin
- AT+INTMOD=1 // Trigger by rising and falling edge
- AT+INTMOD=2 // Trigger by falling edge
- AT+INTMOD=3 // Trigger by rising edge
2.8 Set Calibration
AT Command:
- AT+CAL
Downlink Payload:
- 0x(F2 00)
2.9 Set installation direction
The shortest time of two Alarm packet. (unit: min)
AT Command:
- AT+INSTAL=0
Downlink Payload:
- 0x(F0 00) // Set AT+INSTAL=0
2.10 Set angle alarm
AT Command:
- AT+XALARM=value
- AT+XALARM=min,max
Downlink Payload:
- 0x(F3 00 1E) // Set AT+XALARM=30
- 0x(F3 00 1E 00 50) // Set AT+XALARM=30,80
- 0x(F4 00 1E) // Set AT+YALARM=30
- 0x(F4 00 1E 00 50) // Set AT+YALARM=30,80
2.11 Set alarm mode
AT Command:
- AT+AMOD=1
Downlink Payload:
- 0x(F5 01) // Set AT+AMOD=1
2.12 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)
Note: To disable clock recording, set the following parameters: AT+CLOCKLOG=1,65535,0,0
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).
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.13 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.
2.14 Uplink log query
- AT Command: AT+GETLOG
This command can be used to query upstream logs of data packets.
2.15 Scheduled domain name resolution
This command can be used to resolve domain names regularly.
AT Command:
- AT+DNSTIMER=XX // Unit: hour
After setting this command, domain name resolution will be performed regularly.
2.16 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
2.17 Set the downlink debugging mode(Since firmware v1.3.0)
Feature: Set the conversion between the standard version and 1T version downlinks.
AT command: AT+DOWNTE
Command Example | Function/Parameters | Response/Explanation |
---|---|---|
AT+DOWNTE=? | Get current Settings | 0,0 (default) OK |
AT+DOWNTE=a,b | a: Set the conversion between the downlink of the standard version and 1T version | 0: Set the downlink of the standard version. |
b: Enable/Disable downlink debugging | 0: Disable downlink debugging mode. |
Example:
- AT+DOWNTE=0,1 //Set to standard version downlink, and enable downlink debugging.
- AT+DOWNTE=1,1 //Set to 1T version downlink, and enable downlink debugging.
Downlink Command:
No downlink commands for feature
2.18 Domain name resolution settings(Since firmware v1.3.0)
Feature: Set dynamic domain name resolution IP.
AT command: AT+BKDNS
Command Example | Function/Parameters | Response/Explanation |
---|---|---|
AT+BKDNS=? | Get current Settings | 0,0,NULL (default) OK |
AT+BKDNS=a,b,c |
a: Enable/Disable dynamic domain name resolution. | 1: Disable dynamic domain name update. The ip address will be saved after the domain name is resolved, if the next domain name resolution fails, the last saved ip address will be used. 2: Enable dynamic domain name update. The ip address will be saved after domain name resolution, if the next domain name resolution fails, the last saved ip address will be used, and the domain name resolution will be updated regularly according to the time set by the customer. |
b: Set the time to update the domain name resolution at regular intervals. |
Unit: hour | |
c: Set the IP address manually. | The format is the same as AT+SERVADDR. If domain name resolution fails, this ip address will be used directly, if domain name resolution succeeds, parameter c will be updated to the successfully resolved IP address. |
Example:
- AT+BKDNS=1,0 //Dynamic domain name resolution is disabled.
- AT+BKDNS=2,1 //The dynamic domain name resolution function is enabled and the automatic update time is set to 1 hour.
- AT+BKDNS=2,4,3.69.98.183,1883 //The dynamic domain name resolution function is enabled and the automatic update time is set to 4 hour, and manually set the ip address, if the domain name failed to resolve, it will directly use this ip to communicate. When the next domain name resolution is successful, it will be updated to the ip address of the successful resolution.
Downlink Command:
No downlink commands for feature
3. Configure TS01-NB
3.1 Configure Methods
TS01-NB supports below configure method:
- AT Command via Bluetooth Connection (Recommended): BLE Configure Instruction.
- AT Command via UART Connection : See UART Connection.
3.2 Serial Access Password
After the Bluetooth or UART connection is successful, use the Serial Access Password to enter the AT command window.
The label on the box of the node will print the initial password: AT+PIN=xxxxxx, and directly use the six-digit password to access the AT instruction window.
If you need to change the password, use AT+PWORD=xxxxxx (6 characters), NB nodes only support lowercase letters.
Note: After entering the command, you need to add a line break, and you can also set automatic line breaks in the Bluetooth tool or UART connection tool.
3.3 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
AT+MODEL : Get module information
ATZ : Trig a reset of the MCU
AT+CFGMOD : Working mode selection
AT+DEUI : Get or set the Device ID
AT+CFG : Print all settings
AT+SERVADDR: Get or Set the Server address
AT+TDC : Get or set the application data transmission interval in s
AT+INTMOD : Get or Set the trigger interrupt mode (0:input,1:falling or rising,2:falling,3:rising)
AT+APN : Get or set the APN
AT+5VT : Get or Set extend the time of 5V power
AT+PRO : Get or Set usage agreement (1:COAP,2:UDP,3:MQTT,4:TCP)
AT+RXDL : Get or Set the receiving time
AT+XALARM :ALARM MOD 1:Get or Set alarm of angle X(0-360) ALARM MOD 2: X(-180-180)
AT+YALARM :ALARM MOD 1:Get or Set alarm of angle Y(0-360) ALARM MOD 2: Y(-180-180)
AT+INSTAL:Get or Set the installation direction
AT+CAL:Angle calibration
AT+AMOD:Get or Set the alarm mode
AT+GETSENSORVALUE : Returns the current sensor measurement
AT+DNSCFG : Get or Set DNS Server
AT+CSQTIME : Get or Set the time to join the network
AT+DNSTIMER : Get or Set the NDS timer
AT+TLSMOD : Get or Set the TLS mode
AT+SLEEP : Get or Set the sleep mode
AT+DEBUG : Entering/exiting debugging mode
AT+GETLOG : Print serial port logs
AT+CLOCKLOG: Get or set SHT record time
Coap Management
AT+URI1: Get or set CoAP option 1
AT+URI2: Get or set CoAP option 2
AT+URI3: Get or set CoAP option 3
AT+URI4: Get or set CoAP option 4
MQTT Management
AT+CLIENT : Get or Set the MQTT clientID
AT+UNAME : Get or Set the MQTT Username
AT+PWD : Get or Set the MQTT password
AT+PUBTOPIC: Get or set MQTT publishing topic
AT+SUBTOPIC: Get or set MQTT subscription topic
AT+MQOS : Set the QoS level of MQTT
Information
AT+PWORD : Get or set the System password
AT+FDR1 : Reset parameters to factory default values except for passwords
AT+FDR : Reset Parameters to Factory Default
AT+CDP : Read or Clear cached data
AT+LDATA : Get the last upload data
4. Battery & Power Consumption
TS01-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.
- Update through UART TTL interface : Instruction.
6. FAQ
6.1 How can I access t BC660K-GL AT Commands?
User can access to BC660K-GL directly and send AT Commands.
7. Order Info
Part Number: TS01-NB-XX
XX:
- GE: General version ( Exclude SIM card)
- 1T: with 1NCE * 10 years 500MB SIM card and Pre-configure to ThingsEye server
8. Packing Info
Package Includes:
- TS01-NB NB-IoT Tilting Sensor x 1
- External antenna x 1
Dimension and weight:
- Device Size: cm
- Device Weight: g
- Package Size / pcs : cm
- Weight / pcs : g
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.