This document explains how to set up the SEK-SVM4x sensor module to run on a Raspberry Pi using the provided code.

The SVM4x evaluation kit covers evaluation of the SGP40 and SGP41 sensors.

Your sensor has the five different connectors: VCC, GND, SDA, SCL, SEL (the sixth connector will not be used for now). Use the following pins to connect your SVM4x:

If you don't have a suitable cable at hand, please find the SEK-SVM4x technical description here:

• Install the Raspberry Pi OS on to your Raspberry Pi
• Enable the I2C interface in the raspi-config
• Download the driver for the Sensirion Github Page and extract the .zip on your Raspberry Pi
• Compile the driver

  1. Open a terminal

  2. Navigate to the driver directory. E.g. cd ~/raspberry-pi-i2c-svm4x

  3. Run the make command to compile the driver

     Output:

     rm -f svm41_i2c_example_usage
     cc -Os -Wall -fstrict-aliasing -Wstrict-aliasing=1 -Wsign-conversion -fPIC -I. -o svm41_i2c_example_usage  svm41_i2c.h svm41_i2c.c sensirion_i2c_hal.h sensirion_i2c.h sensirion_i2c.c \
       sensirion_i2c_hal.c sensirion_config.h sensirion_common.h sensirion_common.c svm41_i2c_example_usage.c
     

• Test your connected sensor

  • Run ./svm41_i2c_example_usage in the same directory you used to compile the driver.

    Output:

    Serial number: 0FA3F1F7000003392A3D0240
    Firmware: 3.0 Debug: 0
    Hardware: 3.0
    Protocol: 1.0
    Temperature Offset: 0.00 °C
    Humidity: 47.34 % RH
    Temperature: 28.95 °C
    VOC index: 101.0 VOC index
    NOx index: 1.0 NOx index
    Humidity: 47.35 % RH
    Temperature: 28.98 °C
    VOC index: 101.0 VOC index
    NOx index: 1.0 NOx index
    ...
    

• Ensure that you connected the sensor correctly: All cables are fully plugged in and connected to the correct pin.
• Ensure that I2C is enabled on the Raspberry Pi. For this redo the steps on "Enable the I2C interface in the raspi-config" in the guide above.
• Ensure that your user account has read and write access to the I2C device. If it only works with user root (sudo ./svm41_i2c_example_usage), it's typically due to wrong permission settings.