Interfacing Bosch BME680

RE: Interfacing Bosch BME680

Øyvind — Thu, 05 Dec 2024 09:43:36 GMT

Hey Kaushalya,

[quote user="kaushalyasat"]

I need to relax the sample timing to support my power budget requirements. Does this mean I cant use any other timing than specified in the drivers?

If it is possible, how can I change the sample timing?

[/quote]

I will need to discuss internally with the developers.

[quote user="kaushalyasat"]Thanks again. Is it within SDK folder or within Zephyr folder?[/quote]

This is a driver found in sdk-nrf, so you should call west commands in the nrf folder.

[quote user="kaushalyasat"]It would be great if you can update the driver page to correctly instruct a newcomer which folder he/she should use to update west for BSEC drivers.[/quote]

Yes, that is a very good point. I will notify internally!

Kind regards,
Øyvind

RE: Interfacing Bosch BME680

kaushalyasat — Tue, 03 Dec 2024 22:46:59 GMT

Hi Øyvind,

Thanks.

[quote userid="77062" url="~/f/nordic-q-a/116628/interfacing-bosch-bme680/513159"]Please do not change timing in the drivers[/quote]

I need to relax the sample timing to support my power budget requirements. Does this mean I cant use any other timing than specified in the drivers?

If it is possible, how can I change the sample timing?

[quote userid="77062" url="~/f/nordic-q-a/116628/interfacing-bosch-bme680/513159"]Happy to see you were able to find the correct path and compile.[/quote]

Thanks again. Is it within SDK folder or within Zephyr folder? It would be great if you can update the driver page to correctly instruct a newcomer which folder he/she should use to update west for BSEC drivers.

Cheers,

Kaushalya

RE: Interfacing Bosch BME680

Øyvind — Tue, 03 Dec 2024 10:11:14 GMT

Hello,

[quote user="kaushalyasat"] I can see with my modified timing,[/quote]

What modified timing did you perform? Please do not change timing in the drivers as this can cause issues with the root Bosch defined drivers. Our developers do not recommend changing these values due to the result that you got.

[quote user="kaushalyasat"]but does it matter you run the west update from within SDK folder or zephyr folder?[/quote]

Happy to see you were able to find the correct path and compile.

Kind regards,
Øyvind

RE: Interfacing Bosch BME680

kaushalyasat — Mon, 02 Dec 2024 23:16:48 GMT

Hi,

After further debugging, I can see with my modified timing, I get the ' BSEC_W_SC_CALL_TIMING_VIOLATION' error from 'bsec_sensor_control ()', which is invoked from 'bsec_thread_fn ()'.

The comment of this this error code says 'Difference between actual and defined sampling intervals of bsec_sensor_control() greater than allowed'.

I couldnt find the source of bsec_sensor_control ().

What are the limits of these timings? How can we change the timings to suit our application?

Cheers,

Kaushalya

RE: Interfacing Boche BME680

kaushalyasat — Mon, 02 Dec 2024 03:51:09 GMT

Hi,

I have infact done this modification earlier, but no luck. Strangely I built the project and SDK from scratch at home over the weekend and it was successful!! Only diff I did was I executed the

west config manifest.group-filter +bsec
west update

within different folders. I cant exactly remember which is which, but does it matter you run the west update from within SDK folder or zephyr folder? The BME68X IAQ driver page does not indicate which folder you should be in before executing the west update.

Anyway I did the same today at my office project folder and got it compiled.

Now I can get the BME68x driver reading from my project.

I wanted to play around the sample timings as outlined in the

BSEC_SAMPLE_RATE=BSEC_SAMPLE_RATE_LP
BSEC_GAS_SAMPLE_RATE=BSEC_SAMPLE_RATE_ULP
BSEC_SAMPLE_PERIOD_S=3

I found these timing values are defined in C:\ncs\v2.6.0\modules\lib\bsec\src\inc\bsec_datatypes.h. But when I changed the 'BSEC_SAMPLE_RATE_ULP' and 'BSEC_SAMPLE_RATE_LP' to different values (0.00167f and 0.017f) the driver seemed to stop sending any I2C comms to the BME68x. Any idea why?

Also is there a way to modify these timings without modifying files in the SDK? Update the SDK and you loose all your settings.

Cheers,

Kaushalya

RE: Interfacing Boche BME680

Øyvind — Fri, 29 Nov 2024 09:35:27 GMT

Hello again,

This is a bug and has been fixed in e.g. v2.8.0, but the problem is found in nrf\drivers\sensor\bme68x_iaq\CMakeLists.txt. In this file, ~ line 27, you can see that zephyr_library_compile_definitions_ifdef is pointing to BME68X_IAQ_SAMPLE_RATE_QUICK_ULTRA_LOW_POWER and not CONFIG_BME68X_IAQ_SAMPLE_RATE_QUICK_ULTRA_LOW_POWER

If you replace the whole line with zephyr_library_compile_definitions_ifdef(BME68X_IAQ_SAMPLE_RATE_QUICK_ULTRA_LOW_POWER it should build as intended.

Let me know how that works for you.

KInd regards,
Øyvind

RE: Interfacing Boche BME680

Øyvind — Fri, 29 Nov 2024 08:30:44 GMT

Hi Kaushalya,

my apologies for the late reply, for some reason my answer was not sent yesterday. I need to discuss internally in regards to the driver, and why it fails with QUICK_ULTRA_LOW_POWER and not ULTRA_LOW_POWER.

I hope to have an answer by end of today or Monday.

Kind regards,
Øyvind

RE: Interfacing Boche BME680

kaushalyasat — Fri, 29 Nov 2024 04:56:01 GMT

Hi,

Need some help building the sample with CONFIG_BME68X_IAQ_SAMPLE_RATE_QUICK_ULTRA_LOW_POWER. I get the build errors saying

C:/ncs/v2.6.0/nrf/drivers/sensor/bme68x_iaq/bme68x_iaq.c:35:32: error: 'BSEC_GAS_SAMPLE_RATE' undeclared here
..
C:/ncs/v2.6.0/nrf/drivers/sensor/bme68x_iaq/bme68x_iaq.c:57:32: error: 'BSEC_SAMPLE_RATE' undeclared here
...
C:/ncs/v2.6.0/nrf/drivers/sensor/bme68x_iaq/bme68x_iaq.c:463:35: error: 'BSEC_SAMPLE_PERIOD_S' undeclared

If I use any other such as

CONFIG_BME68X_IAQ_SAMPLE_RATE_ULTRA_LOW_POWER=y, it builds ok.

I cant figure out what is the difference.

Please help.

Cheers,

Kaushalya

RE: Interfacing Boche BME680

kaushalyasat — Thu, 28 Nov 2024 05:34:56 GMT

Hi Øyvind,

1. While I am trying to integrate it with my sensor code, when I add

CONFIG_BME68X_IAQ_SAMPLE_RATE_QUICK_ULTRA_LOW_POWER=y

to my prj.conf, I get build error

C:/ncs/v2.6.0/nrf/drivers/sensor/bme68x_iaq/bme68x_iaq.c:463:35: error: 'BSEC_SAMPLE_PERIOD_S' undeclared

But when I use

CONFIG_BME68X_IAQ_SAMPLE_RATE_ULTRA_LOW_POWER=y

then no prob.

I can see the

BSEC_SAMPLE_PERIOD_S is defined in CMakeLists.txt in the driver folder. Why am I getting a build error when I use

CONFIG_BME68X_IAQ_SAMPLE_RATE_QUICK_ULTRA_LOW_POWER ?

2. Also for a long time all my iaq measurements are static no matter what I do. I always get

iaq: 50; CO2: 500.000000; VOC: 0.499999

But my temp and humidity changes. I had it working in one instance.

All of a sudden my iaq, co2 and voc values start changing. After that they seem to respond correctly.

Does this means BME688 takes some time before the iaq, co2 and voc data becomes available?

Cheers,

Kaushalya

RE: Interfacing Boche BME680

kaushalyasat — Thu, 28 Nov 2024 04:06:10 GMT

Hi Øyvind,

Thanks. I have added the bme68x_irq to my 2.6.0 SDK. However the sample I found was in nrf folder and it would have been much better if this is mentioned in the 'BME68X: Gas Sensor' page, as there are other samples folders as well with bme680.

I managed to get the sample running and can see the iaq, CO2 and VOC readings. I see these increases when I bring a permanent marker near the sensor and goes down after removing it. So I reckon the sensor is working.

[quote userid="77062" url="~/f/nordic-q-a/116628/interfacing-boche-bme680/512272"]Do you actually get an error from your side? Does the sample work out of the box without editing anything[/quote]

I think out of the box it worked. Then I wanted to fetch just individual channels and then I got the kernel panic. For individual channels, I changed the fetch to fetch_chan and specified chan as SENSOR_CHAN_AMBIENT_TEMP. Then I got the kernel panic. Cant figure out the logic behind the assert as it seems like if the chan is not SENSOR_CHAN_ALL, it would make a kernel panic. But after I moved to bme68x_iaq, I haven't noticed that.

But since I now can get the bme68x_irq working, I integrated it to my sensor app, which is a SED. I set following in the prj.conf.

CONFIG_I2C=y
CONFIG_SENSOR=y
CONFIG_SENSOR_INFO=y

CONFIG_BME680=n
CONFIG_BME68X_IAQ=y
CONFIG_CONSOLE=y
CONFIG_LOG=y
CONFIG_BME68X_IAQ_SAMPLE_RATE_ULTRA_LOW_POWER=y

I can see a sample being taken every 5 minutes.

1. My console seems to hang after this sample is taken. No log messages are printed as well.

2. I want to get temp and humidity samples every 60 sec and VOC every 10 minutes. How can I configure the timing?

Cheers,

Kaushalya

RE: Interfacing Boche BME680

Øyvind — Wed, 27 Nov 2024 08:26:05 GMT

[quote user="kaushalyasat"]Unfortunately I cant find any driver like bme68x_irq under my 'drivers/sensor' folder. How can I install the bme68x driver code?[/quote]

Have you followed the documentation for the BME68x driver?

[quote user="kaushalyasat"]This seems like the 'chan' variable has to be SENSOR_CHAN_ALL or otherwise a kernel panic would occur. I want to measure just temp and humidity channel. What is the reason for this _ASSERT ?[/quote]

The __ASSERT_NO_MSG() macro can be used to perform an assertion that reports the failed test and its location, but lacks additional debugging information provided to assist the user in diagnosing the problem; its use is discouraged.

Do you actually get an error from your side? Does the sample work out of the box without editing anything

Kind regards,
Øyvind

RE: Interfacing Boche BME680

kaushalyasat — Wed, 27 Nov 2024 00:42:25 GMT

Hi,

Thanks for the reply.

My SDK is 2.6.0.

2. Unfortunately I cant find any driver like bme68x_irq under my 'drivers/sensor' folder. How can I install the bme68x driver code?

3. I have managed to cut the power by turning off the heater for gas measurements. But I had to comment out the line 219 in bme680.c in 'drivers/sensor/bme680/'. The line is

__ASSERT_NO_MSG(chan == SENSOR_CHAN_ALL)

This seems like the 'chan' variable has to be SENSOR_CHAN_ALL or otherwise a kernel panic would occur. I want to measure just temp and humidity channel. What is the reason for this _ASSERT ?

Cheers,

Kaushalya

RE: Interfacing Boche BME680

Øyvind — Fri, 22 Nov 2024 14:11:14 GMT

Hello,

Both sensors have been in use in our samples and prototyping platforms Thingy:53 and Thingy:91. What version of our SDK are you using? The information below is based on nRF Connect SDK v2.8.0.

[quote user=""]1. I think this is using the Zephyr built in bme680 driver, isn't it?[/quote]

Yes, looking at zephyr\boards\nordic\thingy53\thingy53_nrf5340_common.dtsi

&i2c1 {
	compatible = "nordic,nrf-twim";
	status = "okay";
	clock-frequency = <I2C_BITRATE_FAST>;

	pinctrl-0 = <&i2c1_default>;
	pinctrl-1 = <&i2c1_sleep>;
	pinctrl-names = "default", "sleep";
	bmm150: bmm150@10 {
		compatible = "bosch,bmm150";
		reg = <0x10>;
	};

	bh1749: bh1749@38 {
		compatible = "rohm,bh1749";
		reg = <0x38>;
		int-gpios = <&gpio1 5 (GPIO_PULL_UP | GPIO_ACTIVE_LOW)>;
	};

	bme688: bme688@76 {
		compatible = "bosch,bme680";
		reg = <0x76>;
	};
};

[quote user=""]2. I am evaluating both BME680 and BME688. How can I change code to suit BME688?[/quote]

Have a the look at the BME68x: Gas sensor sample. This supports both sensors. You can also have a look the samples in our SDK that uses these sensors i.e. the sensor module in Asset Tracker v2 or the Bluetooth Mesh: sensor sample.

[quote user=""]3. My case is a battery powered sensor, so I have to make it as much power efficient as possible. The sample program doesnt seem to meet that goal. I tried commenting out each channel and it doesn't seem that affect the power consumption. I tried using 'sensor_sample_fetch_chan (dev, SENSOR_CHAN_AMBIENT_TEMP) just to fetch temp channel, but still same. Any idea why?[/quote]

I'm not that familiar with the BME68x devices. What sample program are you referring to? The Sensors API in the Zephyr OS does have power management features.
There are options to set ultra low power using CONFIG_BME68X_IAQ_SAMPLE_RATE_ULTRA_LOW_POWER=y but I recommend looking through the BME68x driver documentation.

[quote user=""]4. I want to read/write registers of the sensor, but Sensor API doesn't seem to provide any interface. How can I do this?[/quote]

I think you will need to look at the Sensor API

I hope this helps and provides some answers.

Kind regards,
Øyvind