Bosch Shared
- Top Results
See all results
- About BernhardMathias
- About BernhardMathias
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
About BernhardMathias
since
09-18-2019
10-07-2019
BernhardMathias
Member
8
Posts
1
Likes
0
Solutions
10-07-2019
09:59 AM
Ok, let's assume there was an event - even though I'm not sure what happened because the sensor is located in our office room and the air ventilation in the room works well.... and the peak is really high ... I will try to do some further tests..... Best regards!
... View more
10-03-2019
01:50 PM
1 Like
Ok, new testrun and a peak to 1400 ppm in eCO2 occured: this time - stderr was logged -> no error messages - state-file was deleted before the testrun - floating point compensation was enabled - i2c communication was logged (https://www.saleae.com/de/downloads/ , trigger at peak + 500 seconds pre-buffer) Strange here is a break in the gas trendline the same time the eCO2 value jumps: What can be the reason for the strange gas / eCO2 values? I will attach the bsec output as well as the I2C-log. Best regards, Bernhard
... View more
10-02-2019
11:25 AM
Thanks for the quick response, so - the timestamps look ok - not sure about warning/error messages at the moment since I only logged stdout and not stderr 😕 - gas values (I will attach data-files too): - in this testruns I didn't delete the state files - it's possible that the state files were not empty at time of teststart... We will try to do further tests with enabled floating-point compensation, log stderr and also additional some i2c-logging on the raspberry pi
... View more
10-01-2019
03:31 PM
Hi, As described in https://community.bosch-sensortec.com/t5/MEMS-sensors-forum/BME680-measurements/m-p/9353#M1359 we use an example application with a precompiled bsec library for data evaluation (BME680 sensor): https://github.com/alexh-name/bsec_bme680_linux This time we test the BME680 sensor with a rasperry pi zero and the SEN-BME680 eval board (Joy-it) - so we can exclude hardware failures on our side (since the raspberry is used in many other I2C-Applications without any problems ....) Again, the measured eCO2 trendline contains unrealistic jumps and measurement results (eCO2): - Is it possible, that there is a bug in the bsec-library? - Is there a physical explanation for such unrealistic jumps in the trendline? - Maybe the firmware on the BME680 is buggy? Is an update available? Our customers expect somehow realistic eCO2 - values .... I know, it's just an estimation for CO2, and I may expect errors in the range of 100-200 ppm .... But jumps in the range of 600ppm for no reason? Or values in the range of 5000 ppm in a normal office room (I think I should be dead if the values are correct 😉 )? Any help would be great - Thanks in advance! Best regards, Bernhard Mathias
... View more
09-26-2019
02:52 PM
Thanks for the reply - 2) The hardware is already designed and more or less fixed - but our hardware designer fortunately considered the points you mentioned in your post 😉 1+3) This is in fact what we are trying at the moment .... we operate the devices in a more or less stable temperature environment (with minimal processes) and increase the current consumption via CPU-stress tests .... and we log everything we consider as useable on the PCB (CPU-Load, CPU-temperature, current, BME temperature, ...).... The missing part is to find a formula for compensation ..... but we will try 😉
... View more
Latest Tags
No tags yet
Still looking for something?
- Top Results
See all results