Skip to content

Latest commit

 

History

History

RAK12035_RAK4631_LPWAN

README.md

WisBlock Soil Moisture Sensor

This example is for a soil moisture sensor based on the WisBlock RAK4631 Core module ⤴️ and the RAK12023/RAK12035 soil moisture sensor ⤴️.

Hardware used

Power consumption

The application sleeps around between each measurement and puts the soil moisture sensor into sleep as well. But even this solution switches off the power of the sensor, the sleep current is still ~900uA. Still looking into a better solution.

Software used

REMARK

The libraries are all listed in the platformio.ini and are automatically installed when the project is compiled. The RAK12035_SoilMoisture library might not be published yet. It is included in the repo in the lib folder.

How to use it

Compile the firmware and flash it on a WisBlock with RAK4631 and RAK12023 modules installed.

A Setup the LPWAN credentials with one of the options:

  1. Connect over USB to setup the LPWAN credentials. Use the DevEUI printed on the RAK4631, use the AppEUI and AppKey from your LPWAN server. Do NOT activate automatic join yet. As soil moisture levels are not changing very fast, it might be sufficient to set the send frequency to every 3 hours. The send frequency is set in seconds, so the value would be 3 * 60 * 60 ==> 10800 Example AT commands:
AT+NWM=1
AT+NJM=1
AT+DEVEUI=1000000000000001
AT+APPEUI=AB00AB00AB00AB00
AT+APPKEY=AB00AB00AB00AB00AB00AB00AB00AB00
AT+SENDFREQ=3600
Command Explanation
AT+NWM=1 set the node into LoRaWAN mode
AT+NJM=1 set network join method to OTAA
AT+DEVEUI=1000000000000001 set the device EUI, best to use the DevEUI that is printed on the label of your WisBlock Core module
AT+APPEUI=AB00AB00AB00AB00 set the application EUI, required on the LoRaWAN server
AT+APPKEY=AB00AB00AB00AB00AB00AB00AB00AB00 set the application Key, used to encrypt the data packet during network join
AT+SENDFREQ=3600 set the frequency the sensor node will send data packets. 3600 == 60 x 60 seconds == 1 hour

REMARK

The manual for all AT commands can be found here: AT-Commands.md ⤴️

  1. Use the WisBlock Toolbox ⤴️, connect over Bluetooth with the Soil Sensor and setup the credentials. Do NOT activate automatic join yet.

B Calibrate the sensor

As each sensor has a different sensitivity, the sensor needs to be calibrated. Calibration can be done over the AT command interface. The calibration requires two steps, first measure with the sensor in dry air, second measure with the sensor submerged in water (only the tip up to the white line on the sensor).
The calibration needs to be done only once. The calibration values are stored in the RAK12035 sensor. That means if you calibrate the sensor on one RAK4631, you do not need to do it again if you change the RAK4631. The firmware will read the calibration data from the sensor.

  1. Dry calibration.
    Have the sensor in dry air.
    Submit AT command AT+DRY to start the calibration. After the calibration is done, the value is saved in the sensor and the result will be printed in the terminal screen.
  2. Wet calibration.
    Have the sensor submerged in water (only the tip up to the white line on the sensor).
    Submit AT command AT+WET to start the calibration. After the calibration is done, the value is saved in the sensor and the result will be printed in the terminal screen.

Above calibration is a very basic one, if you need better accuracy you need to calibrate the sensor in the soil itself. Which is not a simple thing, as the moisture measurement will be affected by the density of the soil, the amount of fertilizer in the soil, temperature and other factors.
For a calibration in soil, you need to prepare two pots with the same soil (best taken from the field/garden where the sensors will be used later).

  1. Dry calibration: Let one pot dry up complete, make sure the soil is not clumped together and the complete soil in the pot is dried up. Put the sensor complete into the dry soil, make sure it is complete under the surface, only the wire sticking out.
    Submit AT command AT+DRY to start the calibration. After the calibration is done, the value is saved in the sensor and the result will be printed in the terminal screen.
  2. Wet calibration: Poor water into the second pot. Make sure the soil is saturated with water, mix it up well, make sure the soil has everywhere the same level of water saturation. Put the sensor complete into the wet soil, make sure it is complete under the surface, only the wire sticking out.
    Submit AT command AT+WET to start the calibration. After the calibration is done, the value is saved in the sensor and the result will be printed in the terminal screen.

C Setup your LPWAN server application.

Please check tutorials how to setup an LPWAN server application.
Example for Loriot: RAK7258 Loriot ⤴️
Example for AWS: RAK7258 AWS ⤴️
Example for TheThingsNetwork: RAK7258 TTN ⤴️
Example for Chirpstack: RAK7244 Chirpstack ⤴️

D Connect the Soil Sensor to the LPWAN server

To enable connection to the LPWAN server, the sensor node must be set to auto join mode either with AT command over USB or with the WisBlock Toolbox over BLE.

  1. With AT command:
    Reconnect over USB to the sensor node and send the command AT+JOIN=1,1,10,10 to the sensor node. Then restart the node to start the join process.
  2. Over BLE:
    Connect the WisBlock Toolbox to the sensor node. Check the Auto join checkbox, then push the Send button.

Setting up LoRaWAN credentials

The LoRaWAN credentials are defined in include/main.h. But this code supports 2 other methods to change the LoRaWAN credentials on the fly:

1) Setup over BLE

Using the WisBlock Toolbox ⤴️ you can connect to the WisBlock over BLE and setup all LoRaWAN parameters like

  • Region
  • OTAA/ABP
  • Confirmed/Unconfirmed message
  • ...

More details can be found in the WisBlock Toolbox repo ⤴️

The device is advertising over BLE only the first 30 seconds after power up and then again for 15 seconds after wakeup for measurements. The device is advertising as RAK-SOIL-xx where xx is the BLE MAC address of the device.

2) Setup over USB port

Using the AT command interface the WisBlock can be setup over the USB port.

A detailed manual for the AT commands are in AT-Commands.md ⤴️

Example setup for LoRaWAN, OTAA join mode, sending data every 60 minutes. DevEUI, AppEUI and AppKey in this example are random choosen and need to be changed to your setup. You need to have a matching device setup in the LPWAN server.

AT+NWM=1
AT+NJM=1
AT+DEVEUI=1000000000000001
AT+APPEUI=AB00AB00AB00AB00
AT+APPKEY=AB00AB00AB00AB00AB00AB00AB00AB00
AT+SENDFREQ=3600
AT+JOIN=1,1,10,10
Command Explanation
AT+NWM=1 set the node into LoRaWAN mode
AT+NJM=1 set network join method to OTAA
AT+DEVEUI=1000000000000001 set the device EUI, best to use the DevEUI that is printed on the label of your WisBlock Core module
AT+APPEUI=AB00AB00AB00AB00 set the application EUI, required on the LoRaWAN server
AT+APPKEY=AB00AB00AB00AB00AB00AB00AB00AB00 set the application Key, used to encrypt the data packet during network join
AT+SENDFREQ=3600 set the frequency the sensor node will send data packets. 3600 == 60 x 60 seconds == 1 hour
AT+JOIN=1,1,10,10 start to join the network, enables as well auto join after a power up or a device reset

Compiled output

The compiled files are located in the ./Generated folder. Each successful compiled version is named as
WisBlock_SOIL_Vx.y.z_YYYYMMddhhmmss
x.y.z is the version number. The version number is setup in the ./platformio.ini file.
YYYYMMddhhmmss is the timestamp of the compilation.

The generated .hex file can be used as well to update the device over BLE using either WisBlock Toolbox ⤴️ or Nordic nRF Toolbox ⤴️ or nRF Connect ⤴️

Debug options

Debug output can be controlled by defines in the platformio.ini
LIB_DEBUG controls debug output of the SX126x-Arduino LoRaWAN library

  • 0 -> No debug output
  • 1 -> Library debug output (not recommended, can have influence on timing)

API_DEBUG controls debug output of WisBlock API

  • 0 -> No debug output
  • 1 -> WisBlock API debug output

MY_DEBUG controls debug output of the application itself

  • 0 -> No debug output
  • 1 -> Application debug output

NO_BLE_LED controls the BLE status LED

  • 0 -> LED active, blinks while advertising, on when connected
  • 1 -> LED inactive

CFG_DEBUG controls the debug output of the nRF52 BSP. It is recommended to keep it off

Example for no debug output and maximum power savings:

[env:wiscore_rak4631]
platform = nordicnrf52
board = wiscore_rak4631
framework = arduino
build_flags = 
    ; -DCFG_DEBUG=2
	-DSW_VERSION_1=1 ; major version increase on API change / not backwards compatible
	-DSW_VERSION_2=0 ; minor version increase on API change / backward compatible
	-DSW_VERSION_3=0 ; patch version increase on bugfix, no affect on API
	-DLIB_DEBUG=0    ; 0 Disable LoRaWAN debug output
	-DAPI_DEBUG=0    ; 0 Disable WisBlock API debug output
	-DMY_DEBUG=0     ; 0 Disable application debug output
	-DNO_BLE_LED=1   ; 1 Disable blue LED as BLE notificator
lib_deps = 
	beegee-tokyo/WisBlock API
	beegee-tokyo/RAK12035_SoilMoisture
extra_scripts = pre:rename.py