Table of Contents:

• 1. Introduction
  • 1.1 What is SDI-12 to NB-IoT/LTE-M Converter
  • 1.2 ​Features
  • 1.3 Specification
  • 1.4 Connect to SDI-12 Sensor
  • 1.5 Sleep mode and working mode
  • 1.6 Button & LEDs
  • 1.7 BLE connection
  • 1.8 Pin Definitions , Switch & SIM Direction
    • 1.8.1 Jumper JP2
    • 1.8.2 BOOT MODE / SW1
    • 1.8.3 Reset Button
    • 1.8.4 SIM Card Direction
  • 1.9 Mechanical
• 2. Use SDI-12-CB to communicate with IoT Server
  • 2.1 Send data to IoT server via NB-IoT/CAT-M1 network
  • 2.2 ​Payload Types
    • 2.2.1 General Json Format(Type=5)
    • 2.2.2 HEX format Payload(Type=0)
• 3. Configure SDI-12-CB
  • 3.1 Configure Methods
  • 3.2  Serial Access Password
  • 3.3 AT Commands Set
  • 3.4 SDI-12 Related Commands
    • 3.4.1 Basic SDI-12 debug command
      • al!  -- Get SDI-12 sensor Identification
      • aM!,aMC!, aM1!- aM9!, aMC1!- aMC9!
      • aC!, aCC!,  aC1!- aC9!,  aCC1!- aCC9! 
      • aR0!- aR9!,  aRC0!- aRC9!
    • 3.4.2 Advance SDI-12 Debug command
    • 3.4.3 Convert ASCII to String
    • 3.4.4 Define periodically SDI-12 commands and uplink.
  • 3.5 Examples To Set SDI commands
    • 3.5.1 Examples 1 -- General Example
    • 3.5.2 Example 2 -- Connect to Hygrovue10
      • 3.5.2.1 Reference Manual and Command
      • 3.5.2.2 Hardware Connection to SDI-12-CB
      • 3.5.2.3 Commands set in SDI-12-CB and uplink payload
    • 3.5.3 Example 3 -- Connect to SIL-400
      • 3.5.3.1 Reference Manual and Command
      • 3.5.3.2 Hardware Connection to SDI-12-CB
      • 3.5.3.3 Commands set in SDI-12-CB and uplink payload
    • 3.5.4 Example 4 -- Connect to TEROS-12
      • 3.5.4.1 Reference Manual and Command
      • 3.5.4.2 Hardware Connection to SDI-12-CB
      • 3.5.4.3 Commands set in SDI-12-CB and uplink payload
    • 3.5.5 Example 5 -- Connect to SIL-400/TEROS-12 & Hygrovue10
      • 3.5.5.1 Important Notice!
      • 3.5.5.2 Hardware Connection to SDI-12-CB
      • 3.5.5.3 Commands set in SDI-12-CB and uplink payload
    • 3.6.6 Example 6 -- Connect to ENTELECHY-EP_SDI-12
      • 3.6.6.1 Reference Manual and Command
      • 3.6.6.2 Hardware Connection to SDI-12-CB
      • 3.6.6.3 Commands set in SDI-12-CB and uplink payload
  • 3.7 Test Uplink and Change Update Interval
  • 3.8 Trggier an uplink by external interrupt
  • 3.9 Set the output time
  • 3.10 Set the all data mode
  • 3.11 Set the payload version
  • 3.12 Scheduled domain name resolution
  • 3.13 Clock logging
• 4. Battery & Power Consumption
• 5. Firmware update
• 6. FAQ
  • 6.1 How can I access the BG95-NGFF AT Commands?
  • 6.2 How to configure the device through the MQTT subscription function?
  • 6.3 General Manual for -CB , -CS models
• 7. Order Info
• 8. ​Packing Info
• 9. Support

1. Introduction

1.1 What is SDI-12 to NB-IoT/LTE-M Converter

The Dragino SDI-12-CB is a SDI-12 to NB-IoT/LYE-M Converter designed for Smart Agriculture solution.

SDI-12 (Serial Digital Interface at 1200 baud) is an asynchronous serial communications protocol for intelligent sensors that monitor environment data. SDI-12 protocol is widely used in Agriculture sensor and Weather Station sensors.

SDI-12-CB has SDI-12 interface and support 12v output to power external SDI-12 sensor. It can get the environment data from SDI-12 sensor and sends out the data via NB-IoT/CAT-M1 wireless protocol.

SDI-12-CB supports different uplink methods including MQTT, MQTTs, UDP, TCP or CoAP for different application requirement, and support uplinks to various IoT Servers.

SDI-12-CB supports BLE configure and OTA update which make user easy to use.

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

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

1.2 ​Features

• For -NB Bands: B1/B2/B3/B4/B5/B8/B12/B13/B17/B18/B19/B20/B25/B28/B66/B70/B85
• For -CB Bands: B1/B2/B3/B4/B5/B8/B12/B13//B18/B19/B20/B25/B28/B66/B71/B85
• CAT-M1 / LTE-M Bands: B1/B2/B3/B4/B5/B8/B12/B13/B18/B19/B20/B25/B26/B27/B28/B66/B85
• Ultra-low power consumption
• Controllable 3.3v, 5v and 12v output to power external sensor
• SDI-12 Protocol to connect to SDI-12 Sensor
• Multiply Sampling and one uplink
• GNSS for Location Report
• Support Bluetooth v5.1 remote configure and update firmware
• Uplink on periodically
• Downlink to change configure
• 8500mAh Battery for long term use
• Uplink via MQTT, MQTTs, TCP, UDP or CoAP
• Nano SIM card slot for NB-IoT SIM

1.3 Specification

Common DC Characteristics:

• Supply Voltage: 2.6v ~ 3.6v
• Support current: 5V 300mA, 12V 100mA
• Operating Temperature: -40 ~ 85°C

Current Input (DC) Measuring :

• Range: 0 ~ 20mA
• Accuracy: 0.02mA
• Resolution: 0.001mA

Voltage Input Measuring:

• Range: 0 ~ 30v
• Accuracy: 0.02v
• Resolution: 0.001v

NB-IoT Spec:

NB-IoT Module: BG95-NGFF

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 Connect to SDI-12 Sensor

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

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

SDI-12-CB 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

SDI-12-CB use the mother board which as below.

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

2. Use SDI-12-CB to communicate with IoT Server

2.1 Send data to IoT server via NB-IoT/CAT-M1 network

The SDI-12-CB is equipped with a NB-IoT module, the pre-loaded firmware in SDI-12-CB 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 SDI-12-CB.

Below shows the network structure:

There are two version: -GE and -1T version of SDI-12-CB.

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 SDI-12-CB 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.

1T Version: This version has 1NCE SIM card pre-installed and configure to send value to ThingsEye. User Just need to select the sensor type in ThingsEyeand Activate SDI-12-CB and user will be able to see data in ThingsEye. See here for ThingsEye Config Instruction.

2.2 ​Payload Types

To meet different server requirement, SDI-12-CB supports different payload type.

Includes:

• General JSON format payload. (Type=5)

• HEX format Payload. (Type=0)

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,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":"864370064394515","Model":"SDI12-CB","Payload":"010+1.30+26.9GmD","battery":3.639,"signal":27,"latitude":22.705860,"longitude":114.244000,"gps_time":"2024-07-30T06:01:44Z","1":["01","2024-07-30T01:29:39Z"],"2":["01","2024-07-30T01:14:33Z"],"3":["01","2024-07-30T00:28:58Z"],"4":["01","2024-07-30T00:13:58Z"],"5":["01","2024-07-29T23:58:58Z"],"6":["01","2024-07-29T23:43:58Z"],"7":["01","2024-07-29T23:28:58Z"],"8":["01","2024-07-29T23:13:58Z"]}

2.2.2 HEX format Payload(Type=0)

This is the HEX Format. As below:

f86437006439451547650e171a0000015a78d606cf33d866a89e6266a89e6201302b302e39342b32382e364a634366a89c8e01302b312e31332b32392e3348735766a8990a01302b312e31332b32392e3144755666a8951d01302b312e36312b32362e3146705166a894e101302b312e36312b32362e3146705166a894a501302b312e36312b32362e3146705166a8946901302b312e36302b32362e314b745066a8942d01302b312e36302b32362e314b745066a893f101302b312e36302b32362e314b7450

Version:

These bytes include the hardware and software version.

Higher byte: Specify Sensor Model: 0x476 for SDI-12-CB

Lower byte: Specify the software version: 0x65=101, means firmware version 1.0.1

BAT (Battery Info):

Check the battery voltage for SDI-12-CB.

Ex1: 0x0df4 =  3572mV

Ex2: 0x0B49 = 2889mV

Signal Strength:

NB-IoT Network signal Strength.

Ex1: 0x1a = 26

0        -113dBm or less

1        -111dBm

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

31      -51dBm or greater

99      Not known or not detectable

GPIO_EXTI Level:

GPIO_EXTI is used as Interrupt Pin.

Example:

01(H): GPIO_EXTI pin is high level.

00(L): GPIO_EXTI pin is low level.

GPIO_EXTI Flag:

This data field shows if this packet is generated by Interrupt Pin or not.  

Note: The Interrupt Pin is a separate pin in the screw terminal.

Example:

0x00: Normal uplink packet.

0x01: Interrupt Uplink Packet.

Latitude:

Example: 0x015A7A7A(H)=22706810(D)=22.706810

Longitude:

Example: 0x06CF33CE(H)=114242510(D)=114.242510

TimeStamp & GPS_Timestamp:   

Unit TimeStamp Example: 66A89E62(H) = 1692587855(D)

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

Payload_version: 

The payload version number is used to parse different decodes.

SDI12_sensor_data:

The data returned by the SDI-12 sensor or UART sensor needs to be cut out the AT+DATACUTx  or AT+ALLDATAMOD commands.

3. Configure SDI-12-CB

3.1 Configure Methods

SDI-12-CB 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), -CB 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+DEUI : Get or set the Device ID

AT+SLEEP : Get or set the sleep status

AT+DEBUG : Set more info output

AT+SERVADDR: Get or Set the Server address

AT+TDC : Get or set the application data transmission interval in s

AT+APN : Get or set the APN

AT+12VT : Get or Set extend the time of 12V power

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

AT+3V3T : Get or Set extend the time of 3V3 power

AT+INTMOD : Get or Set the trigger interrupt mode (0:input,1:falling or rising,2:falling,3:rising)

AT+PRO : Get or Set usage agreement (1:COAP,2:UDP,3:MQTT,4:TCP)

AT+RXDL : Get or Set the receiving time

AT+CDP : Read or Clear cached data

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+GDNS : Get or Set the DNS

AT+TLSMOD : Get or Set the TLS mode

AT+MQOS : Set the QoS level of MQTT

AT+IPTYPE : Set the IPv4 or IPv6

AT+QSW : Power on and power off BG95 module

AT+ADDRI: Send aI command to SDI12 sensor

AT+ADDRM: Send aM command to SDI12 sensor

AT+ADDRC: Send aC command to SDI12 sensor

AT+ADDRR: Send aR command to SDI12 sensor

AT+CMDEAR: Erase command(number of begin to number of ending)

AT+PAYVER: Get or Set payload version

AT+ALLDATAMOD: Get or Set mode of all data is cuted

AT+CONVFORM: Conversion between characters and their ASCII

AT+COMMAND: Send data of command1-15 to SDI12 deceive for payload

AT+DATACUT: Cut receive data after use command1-15

AT+CFGDEV: Send data to SDI12 deceive

AT+CLOCKLOG: Enable or Disable Clock Logging

AT+TIMESTAMP : Get or Set UNIX timestamp in second

AT+GETLOG : Print serial port logs

AT+CFG : Print all settings

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

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

AT+URI5: Get or set CoAP option 5

AT+URI6: Get or set CoAP option 6

AT+URI7: Get or set CoAP option 7

AT+URI8: Get or set CoAP option 8

GPS

AT+GNSST : Extend the time to turn on GNSS

AT+GPS : Turn off and on GPS

AT+GTDC : Get or set GPS positioning interval in units of h

Information           

AT+FDR1 : Reset parameters to factory default values except for passwords

AT+FDR : Reset Parameters to Factory Default

AT+PWORD : Get or set the System password

AT+LDATA : Get the last upload data

3.4 SDI-12 Related Commands

User need to configure SDI-12-CB to communicate with SDI-12 sensors otherwise the uplink payload will only include a few bytes.

3.4.1 Basic SDI-12 debug command

User can run some basic SDI-12 command to debug the connection to the SDI-12 sensor. These commands can be sent via AT Command or NB-IoT downlink command.

If SDI-12 sensor return value after get these commands, SDI-12-CB will uplink the return on FPORT=100, otherwise, if there is no response from SDI-12 sensor. SDI-12-CB will uplink NULL (0x 4E 55 4C 4C) to server.

The following is the display information on the serial port and the server.

al!  -- Get SDI-12 sensor Identification

• AT Command:  AT+ADDRI=aa
• NB-IoT Downlink(prefix 0xAA00):  AA 00 aa

Parameter:  aa: ASCII value of SDI-12 sensor address in downlink or HEX value in AT Command)

Example :   AT+ADDRI=0  ( Equal to downlink: 0x AA 00 30)

The following is the display information on the serial port and the server.

aM!,aMC!, aM1!- aM9!, aMC1!- aMC9!

aM! : Start Non-Concurrent Measurement

aMC! : Start Non-Concurrent Measurement – Request CRC

aM1!- aM9! : Additional Measurements

aMC1!- aMC9! : Additional Measurements – Request CRC

• AT Command : AT+ADDRM=0,1,0,1 

aa: SDI-12 sensor address.

bb: 0: no CRC, 1: request CRC

cc: 1-9: Additional Measurement, 0: no additional measurement

dd: delay (in second) to send aD0! to get return.

The following is the display information on the serial port and the server.

aC!, aCC!,  aC1!- aC9!,  aCC1!- aCC9! 

aC! : Start Concurrent Measurement

aCC! : Start Concurrent Measurement – Request CRC

aC1!- aC9! : Start Additional Concurrent Measurements

aCC1!- aCC9! : Start Additional Concurrent Measurements – Request CRC

• AT Command : AT+ADDRC=0,1,0,1  

aa: SDI-12 sensor address.

bb: 0: no CRC, 1: request CRC

cc: 1-9: Additional Measurement, 0: no additional measurement

dd: delay (in second) to send aD0! to get return.

The following is the display information on the serial port and the server.

aR0!- aR9!,  aRC0!- aRC9!

Start Continuous Measurement

Start Continuous Measurement – Request CRC

• AT Command : AT+ADDRR=0,1,0,1  

aa: SDI-12 sensor address.

bb: 0: no CRC, 1: request CRC

cc: 1-9: Additional Measurement, 0: no additional measurement

dd: delay (in second) to send aD0! to get return.

The following is the display information on the serial port and the server.

3.4.2 Advance SDI-12 Debug command

This command can be used to debug all SDI-12 command. 

Example1:  AT+CFGDEV =0RC0!,1 

0RC0! : SDI-12 Command,

1 : Delay 1 second.  ( 0: 810 mini-second)

The following is the display information on the serial port and the server.

Example2:  AT+CFGDEV =0M!,1,1

0M! : SDI-12 Command,

1 : Delay 1 second.  ( 0: 810 mini-second)

1 : Use aD0! command access.

The following is the display information on the serial port and the server.

3.4.3 Convert ASCII to String

This command is used to convert between ASCII and String format.

AT+CONVFORM ( Max length: 80 bytes)

Example:

1) AT+CONVFORM=0, string Convert String from String to ASCII

2) AT+CONVFORM=1, ASCII Convert ASCII to String.

3.4.4 Define periodically SDI-12 commands and uplink.

AT+COMMANDx & AT+DATACUTx

User can define max 15 SDI-12 Commands (AT+COMMAND1 ~ AT+COMMANDF). On each uplink period (TDC time, default 20 minutes), SDI-12-CB will send these SDI-12 commands and wait for return from SDI-12 sensors. SDI-12-CB will then combine these returns and uplink via NB-IoT. 

• AT Command:

AT+COMMANDx=var1,var2,var3,var4.

var1: SDI-12 command , for example: 0RC0!

var2: Wait timeout for return. (unit: second)

var3: Whether to send addrD0! to get return after var2 timeout. 0: Don't Send addrD0! ; 1: Send addrD0!.

var4: validation check for return. If return invalid, SDI-12-CB will resend this command. Max 3 retries.

0  No validation check;

1  Check if return chars are printable char(0x20 ~ 0x7E);

2  Check if there is return from SDI-12 sensor

3  Check if return pass CRC check ( SDI-12 command var1 must include CRC request);

Each AT+COMMANDx is followed by a AT+DATACUT command. AT+DATACUT command is used to take the useful string from the SDI-12 sensor so the final payload will have the minimum length to uplink.

AT+DATACUTx : This command defines how to handle the return from AT+COMMANDx, max return length is 100 bytes.

For example, if return from AT+COMMAND1 is “013METER   TER12 112T12-00024895<CR><LF>” , Below AT+DATACUT1 will get different result to combine payload:

Note : if user use AT+COMMANDx to add a new command, he also need to send AT+DATACUTx downlink.

Clear SDI12 Command

The AT+COMMANDx and AT+DATACUTx settings are stored in special location, user can use below command to clear them.

• AT Command:

AT+CMDEAR=mm,nn   mm: start position of erase ,nn: stop position of erase

Etc. AT+CMDEAR=1,10 means erase AT+COMMAND1/AT+DATACUT1 to AT+COMMAND10/AT+DATACUT10

command combination

Below shows a screen shot how the results combines together to a uplink payload.

If user don't want to use DATACUT for some command, he simply want to uplink all returns. AT+ALLDATAMOD can be set to 1.

AT+ALLDATAMOD will simply get all return and don't do CRC check as result for SDI-12 command. AT+DATACUTx command has higher priority, if AT+DATACUTx has been set, AT+ALLDATAMOD will be ignore for this SDI-12 command.

For example:  as below photo, AT+ALLDATAMOD=1, but AT+DATACUT1&2 has been set, AT+DATACUT1 &2will be still effect the result.

If AT+ALLDATAMOD=1, FX,X will be added in the payload, FX specify which command is used and X specify the length of return（Hex format）, (X) in JSON format will be added to the payload, where X represents the command number.

for example in above screen, F1 23 means the return is from AT+COMMAND1 and the return is 35 bytes.

3.5 Examples To Set SDI commands

Note: The reading sensor command method of the NB series SDI12 converter is the same as that of the LORA series SDI12 converter.

3.5.1 Examples 1 -- General Example

COM port and SDI-12 sensor communication converted to SDI-12-CB and SDI-12 sensor communication.

1) The AT+COMMANDx command is applied to the red arrow part, and sends the SDI12 command to the SDI12 sensor:

a. Send the first command and get the first reply：

AT+COMMANDx=1I!,0,0,1

b. Send the second command and get the second reply：

AT+COMMANDx=2I!,0,0,1

c. Send the third command and get the third reply：

AT+COMMANDx=3I!,0,0,1

d. Send the fourth command and get the fourth reply：

AT+COMMANDx=4I!,0,0,1

e. Send the fifth command plus the sixth command, get the sixth reply：

AT+COMMANDx=1M!,2,1,1

f. Send the seventh command plus the eighth command, get the eighth reply：

AT+COMMANDx=2M!,2,1,1

g. Send the ninth command plus the tenth command, get the tenth reply：

AT+COMMANDx=3M!,1,1,1

h. Send the eleventh command plus the twelfth command, get the twelfth reply：

AT+COMMANDx=4M!,1,1,1

2) The AT+DATACUTx command is applied to the green arrow part, receiving and cut out data from the SDI12 sensor：

a. The first reply, all 34 characters: ”113TRUEBNERSMT100038220303182331<CR><LF>”

Cut out all characters: AT+ALLDATAMOD=1  or  AT+DATACUTx=34,2,1~34;

b. The sixth reply, all 31 characters：”1+19210+1.04+0.00+22.49+11.75<CR><LF>”

Cut out all characters: AT+ALLDATAMOD=1  or  AT+DATACUTx=31,2,1~31;

c. The eighth reply, all 31 characters：”2+18990+1.08+0.00+22.24+11.80<CR><LF>”

Cut out all characters: AT+ALLDATAMOD=1  or  AT+DATACUTx=31,2,1~31;

d. The tenth reply, all 15 characters：”3-2919.8+24.0<CR><LF>”

Cut out all characters: AT+ALLDATAMOD=1  or  AT+DATACUTx=15,2,1~15;

e. The twelfth reply, all 25 characters：”4+30.8+22.84+4.7+954.38<CR><LF>”

Partial cut, the cut sensor address and the first two parameters：AT+DATACUTx=25,2,1~12, cut out the character field ” 4+30.8+22.84”.

3.5.2 Example 2 -- Connect to Hygrovue10

3.5.2.1 Reference Manual and Command

• Hygrovue10 Product Page

• Commands to be used in PC and output.

1. check device address

2. change device address

3. check device ID

4. start measure

5. Get Meausre result

3.5.2.2 Hardware Connection to SDI-12-CB

3.5.2.3 Commands set in SDI-12-CB and uplink payload

3.5.3 Example 3 -- Connect to SIL-400

3.5.3.1 Reference Manual and Command

• SIL-400 Product Page

• Commands to be used in PC and output.

1. check device address

2. change device address

3. check device ID

4. start measure

5. Get Meausre result

3.5.3.2 Hardware Connection to SDI-12-CB

3.5.3.3 Commands set in SDI-12-CB and uplink payload

3.5.4 Example 4 -- Connect to TEROS-12

3.5.4.1 Reference Manual and Command

• TEROS-12 Product Page

• Commands to be used in PC and output.

1.check device address

2.change device address

3.check device ID

4.start measure

5.Get Meausre result

3.5.4.2 Hardware Connection to SDI-12-CB

3.5.4.3 Commands set in SDI-12-CB and uplink payload

3.5.5 Example 5 -- Connect to SIL-400/TEROS-12 & Hygrovue10

3.5.5.1 Important Notice!

• The product page and reference command see above example 2,3,4

• All of these SDI-12 sensors use the same address (address 0) by default. So we need to change their address to different address, by using aAb! command. See above example.

• The sensor needs to be powered to a steady statue. So the 12VT time need to be set to the maximum stable time for the sensors. in this example, it is 13 seconds.

• If these SDI-12 sensors are powered by external power source. It will add 300uA in the total current in SDI-12-CB.

3.5.5.2 Hardware Connection to SDI-12-CB

3.5.5.3 Commands set in SDI-12-CB and uplink payload

3.6.6 Example 6 -- Connect to ENTELECHY-EP_SDI-12

3.6.6.1 Reference Manual and Command

• https://enviroprosoilprobes.com/wp-content/uploads/2019/11/ENTELECHY-EP_SDI-12-Commands.pdf

• Commands to be used in PC and output.

1.check device address

2.change device address

3.check device ID

4.start measure

5.Get Meausre result

3.6.6.2 Hardware Connection to SDI-12-CB

3.6.6.3 Commands set in SDI-12-CB and uplink payload

3.7 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.

3.8 Trggier an uplink by external interrupt

SDI-12-CB has an external trigger interrupt function. Users can use the GPIO_EXTI 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

3.9 Set the output time

Feature, Control the output 3V3 , 5V or 12V.

AT Command: AT+3V3T

AT Command: AT+5VT

AT Command: AT+12VT 

3.10 Set the all data mode

Feature, Set the all data mode.

AT Command: AT+ALLDATAMOD

3.11 Set the payload version

Feature, Set the payload version.

AT Command: AT+PAYVER

3.12 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.

3.13 Clock logging

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.

4. Battery & Power Consumption

SDI-12-CB 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 the BG95-NGFF AT Commands?

User can access to BG95-NGFF directly and send AT Commands.

See BG95-NGFF AT Command set

6.2 How to configure the device through the MQTT subscription function?

Subscription content: {AT COMMAND}

Example:

Setting AT+5VT=500 through Node-RED requires MQTT to send the content {AT+5VT=500}.

The serial port displays:

6.3 General Manual for -CB , -CS models

Users can follow the instructions in this link to see how to configure to connect to different servers.

7. Order Info

Part Number: SDI-12-CB-XX-YY

XX: 

• GE: General version ( Exclude SIM card)

• 1T: with 1NCE* 10 years 500MB SIM card and Pre-configure to ThingsEye server

YY: The grand connector hole size

• M12: M12 hole

• M16: M16 hole

8. ​Packing Info

Package Includes:

• SDI-12-CB SDI-12 to NB-IoT/LTE-M Converter  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.