<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:webfeeds="http://webfeeds.org/rss/1.0">
    <channel>
        <title><![CDATA[Bosch Sensortec Community]]></title>
        <description><![CDATA[Bosch Sensortec Community]]></description>
        <link>https://community.bosch-sensortec.com</link>
        <generator>Bettermode RSS Generator</generator>
        <lastBuildDate>Sat, 23 May 2026 19:31:57 GMT</lastBuildDate>
        <atom:link href="https://community.bosch-sensortec.com/rss/feed" rel="self" type="application/rss+xml"/>
        <pubDate>Sat, 23 May 2026 19:31:57 GMT</pubDate>
        <copyright><![CDATA[2026 Bosch Sensortec Community]]></copyright>
        <language><![CDATA[en-US]]></language>
        <ttl>60</ttl>
        <webfeeds:icon></webfeeds:icon>
        <webfeeds:related layout="card" target="browser"/>
        <item>
            <title><![CDATA[Looking for small-quantity / hobbyist purchase options for BME690 or BMI323 in Germany]]></title>
            <description><![CDATA[Hello,

I am currently experimenting with Bosch Sensortec sensors for personal ESP32 and embedded projects.

I am especially interested in:

 * BME690

 * BMI323

However, most distributors I found either:

 * require ...]]></description>
            <link>https://community.bosch-sensortec.com/mems-sensors-forum-jrmujtaw/post/looking-for-small-quantity-hobbyist-purchase-options-for-bme690-or-PZpZSAgauj1JyBL</link>
            <guid isPermaLink="true">https://community.bosch-sensortec.com/mems-sensors-forum-jrmujtaw/post/looking-for-small-quantity-hobbyist-purchase-options-for-bme690-or-PZpZSAgauj1JyBL</guid>
            <dc:creator><![CDATA[weti]]></dc:creator>
            <pubDate>Thu, 21 May 2026 11:00:11 GMT</pubDate>
            <content:encoded><![CDATA[<p>Hello,</p><p>I am currently experimenting with Bosch Sensortec sensors for personal ESP32 and embedded projects.</p><p>I am especially interested in:</p><ul><li><p>BME690</p></li><li><p>BMI323</p></li></ul><p>However, most distributors I found either:</p><ul><li><p>require industrial/bulk ordering</p></li><li><p>or have very high shipping costs to Germany/Europe.</p></li></ul><p>Are there recommended distributors, maker boards, sample options, or hobbyist-friendly ways to purchase these sensors in small quantities within Europe?</p><p>Thanks.<br><br>(I hope this is the right place to ask 😄 )</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[BMP390 RoHS and REACH compliance status]]></title>
            <description><![CDATA[Does BMP390 comply with RoHS and REACH?
If it does, please issue a certificate of conformity.]]></description>
            <link>https://community.bosch-sensortec.com/mems-sensors-forum-jrmujtaw/post/bmp390-rohs-and-reach-compliance-status-I3mH1masxrj1Ao8</link>
            <guid isPermaLink="true">https://community.bosch-sensortec.com/mems-sensors-forum-jrmujtaw/post/bmp390-rohs-and-reach-compliance-status-I3mH1masxrj1Ao8</guid>
            <category><![CDATA[BMP390]]></category>
            <dc:creator><![CDATA[YUKI]]></dc:creator>
            <pubDate>Thu, 21 May 2026 01:17:55 GMT</pubDate>
            <content:encoded><![CDATA[<p>Does BMP390 comply with RoHS and REACH?<br>If it does, please issue a certificate of conformity.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[BMM350 RoHS and REACH compliance status]]></title>
            <description><![CDATA[Does BMM350 comply with RoHS and REACH?
If it does, please issue a certificate of conformity.]]></description>
            <link>https://community.bosch-sensortec.com/mems-sensors-forum-jrmujtaw/post/bmm350-rohs-and-reach-compliance-status-SjrA9ISN2306m61</link>
            <guid isPermaLink="true">https://community.bosch-sensortec.com/mems-sensors-forum-jrmujtaw/post/bmm350-rohs-and-reach-compliance-status-SjrA9ISN2306m61</guid>
            <category><![CDATA[BMM350]]></category>
            <dc:creator><![CDATA[YUKI]]></dc:creator>
            <pubDate>Thu, 21 May 2026 01:15:37 GMT</pubDate>
            <content:encoded><![CDATA[<p>Does BMM350 comply with RoHS and REACH?<br>If it does, please issue a certificate of conformity.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Best BSEC outputs to use as features for time-series forecasting?]]></title>
            <description><![CDATA[I'm exploring sequence-model forecasting on top of BME680 / BSEC output and would appreciate input from anyone who has used BSEC in a downstream ML pipeline.

Context: we're integrating BME680 into a ...]]></description>
            <link>https://community.bosch-sensortec.com/mems-sensors-forum-jrmujtaw/post/best-bsec-outputs-to-use-as-features-for-time-series-forecasting-CHnaJiKg1s30APT</link>
            <guid isPermaLink="true">https://community.bosch-sensortec.com/mems-sensors-forum-jrmujtaw/post/best-bsec-outputs-to-use-as-features-for-time-series-forecasting-CHnaJiKg1s30APT</guid>
            <category><![CDATA[BME680]]></category>
            <dc:creator><![CDATA[JuergenP]]></dc:creator>
            <pubDate>Wed, 20 May 2026 14:42:50 GMT</pubDate>
            <content:encoded><![CDATA[<p>I'm exploring sequence-model forecasting on top of BME680 / BSEC output and would appreciate input from anyone who has used BSEC in a downstream ML pipeline.    </p><p>Context: we're integrating BME680 into a self-hosted AI platform (Eldric — <a href="https://eldric.ai" rel="noopener noreferrer nofollow" class="text-interactive hover:text-interactive-hovered">https://eldric.ai</a>) where an xLSTM-based forecaster (TiRex) consumes telemetry windows for anomaly detection and short-horizon prediction. <br><br>Before we commit to a feature set, I want to make sure we pick the BSEC outputs that    actually carry predictive signal, not just the ones that look richest on paper.   </p><p> A few concrete questions:   </p><p> 1. Which BSEC outputs survive the IAQ-accuracy=0 startup window cleanly? During cold start we still need stable features. Is raw gas resistance the more useful early signal, given that IAQ depends on the burn-in period?   </p><p>2. Static IAQ vs ambient IAQ as ML features — has anyone compared them empirically? My intuition is that static IAQ generalises better across environments, but I'd like real-world experience.   </p><p>3. Sampling-rate tradeoffs (ULP / LP / continuous) when the downstream model expects regular intervals. Do you resample BSEC output before feeding it to the model, or run BSEC at a fixed continuous rate and let the model see the raw cadence?   </p><p>4. State persistence across power cycles — what's the cleanest pattern to keep BSEC state and the forecaster's hidden state aligned after a restart? Save both on the same cadence, or treat BSEC state as the source of truth and warm up the model from it?   </p><p> If anyone has benchmarks or has published a BSEC-to-ML pipeline, I'd be glad for pointers. Happy to share findings back here once we've run the first set of experiments.  </p><div data-type="embed" data-id="J25UbgrYLlNara6mRh9gx" data-embed-url="https://eldric.ai"></div>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[BME280 Humidity Value wrong, reconditioning does not seem to help.]]></title>
            <description><![CDATA[We have a number of BME280 sensors installed on a custom PCB, and they are all reporting erroneous humidity readings. Temperature and pressure are fine. Humidity is off 20% or more, sometimes always ...]]></description>
            <link>https://community.bosch-sensortec.com/mems-sensors-forum-jrmujtaw/post/bme280-humidity-value-wrong-reconditioning-does-not-seem-to-help-8KUXIRP1tIJxyc6</link>
            <guid isPermaLink="true">https://community.bosch-sensortec.com/mems-sensors-forum-jrmujtaw/post/bme280-humidity-value-wrong-reconditioning-does-not-seem-to-help-8KUXIRP1tIJxyc6</guid>
            <category><![CDATA[BME280]]></category>
            <dc:creator><![CDATA[EngineerNH]]></dc:creator>
            <pubDate>Wed, 20 May 2026 12:54:02 GMT</pubDate>
            <content:encoded><![CDATA[<p>We have a number of BME280 sensors installed on a custom PCB, and they are all reporting erroneous humidity readings. Temperature and pressure are fine. Humidity is off 20% or more, sometimes always reporting 100%. We tried reconditioning the sensors per the datasheet but that did not help. Any ideas? Our contract manufacturer states they are soldered properly, with proper reflow temperature.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[BME690 + Application Board 3.1 not detected in AI-Studio (Windows) despite power LED ON]]></title>
            <description><![CDATA[I am currently trying to set up a BME690 8x Shuttle Board with Application Board 3.1 using BME AI-Studio Desktop (Windows) for VOC data acquisition.


SETUP:

 * Application Board 3.1

 * Shuttle Board: BME690 8x ...]]></description>
            <link>https://community.bosch-sensortec.com/mems-sensors-forum-jrmujtaw/post/bme690-application-board-3-1-not-detected-in-ai-studio-windows-aruWXsaWJ6raBW9</link>
            <guid isPermaLink="true">https://community.bosch-sensortec.com/mems-sensors-forum-jrmujtaw/post/bme690-application-board-3-1-not-detected-in-ai-studio-windows-aruWXsaWJ6raBW9</guid>
            <dc:creator><![CDATA[Ahmad]]></dc:creator>
            <pubDate>Mon, 18 May 2026 16:22:49 GMT</pubDate>
            <content:encoded><![CDATA[<p>I am currently trying to set up a <strong>BME690 8x Shuttle Board with Application Board 3.1</strong> using <strong>BME AI-Studio Desktop (Windows)</strong> for VOC data acquisition.</p><h3 class="text-lg" data-toc-id="fd93f07b-327e-4f5c-96ab-9cac6963c88c" id="fd93f07b-327e-4f5c-96ab-9cac6963c88c">Setup:</h3><ul><li><p>Application Board 3.1</p></li><li><p>Shuttle Board: BME690 8x sensor board</p></li><li><p>OS: Windows 10/11</p></li><li><p>Software: BME AI-Studio Desktop (latest version)</p></li><li><p>USB cable: USB A to micro-USB (USB 2.0 data + power cable)</p></li></ul><h3 class="text-lg" data-toc-id="a3e66fce-3c69-486f-8ba1-913b7f6d8785" id="a3e66fce-3c69-486f-8ba1-913b7f6d8785">Issue:</h3><ul><li><p>The Application Board powers ON (red LEDs are ON)</p></li><li><p>However, <strong>AI-Studio does not detect any device</strong></p></li><li><p>No board / sensor appears inside the software</p></li><li><p>No communication or sensor data is shown</p></li></ul><p>What drivers or firmware steps are required for first-time connection of Application Board 3.1 with AI-Studio?<br>Is COINES SDK or Development Kit software driver installation required before AI-Studio can detect the board?</p><p>Any guidance would be appreciated. Thank you!</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to export a BME690 AI model from BME AI-Studio to a BSEC release and deploy it on ESP32/STM32?]]></title>
            <description><![CDATA[Hello Bosch Sensortec team,

I am currently using the BME690 with Shuttle Board 8.0, Application Board 3.1, and BME AI-Studio. I have trained an AI model in BME AI-Studio for gas-pattern classification....]]></description>
            <link>https://community.bosch-sensortec.com/mems-sensors-forum-jrmujtaw/post/how-to-export-a-bme690-ai-model-from-bme-ai-studio-to-a-bsec-release-and-dRxcHtmr7jFOpdo</link>
            <guid isPermaLink="true">https://community.bosch-sensortec.com/mems-sensors-forum-jrmujtaw/post/how-to-export-a-bme690-ai-model-from-bme-ai-studio-to-a-bsec-release-and-dRxcHtmr7jFOpdo</guid>
            <category><![CDATA[ARDUINO]]></category>
            <category><![CDATA[BME690 X8]]></category>
            <category><![CDATA[BSEC]]></category>
            <category><![CDATA[ESP32]]></category>
            <category><![CDATA[I2C]]></category>
            <dc:creator><![CDATA[Kai]]></dc:creator>
            <pubDate>Mon, 18 May 2026 09:16:58 GMT</pubDate>
            <content:encoded><![CDATA[<p>Hello Bosch Sensortec team,</p><p>I am currently using the BME690 with Shuttle Board 8.0, Application Board 3.1, and BME AI-Studio. I have trained an AI model in BME AI-Studio for gas-pattern classification.</p><p>Now I would like to deploy this trained model on my own MCU platform, for example ESP32 or STM32, so that the BME690 can run in the final embedded system and output the correct classification/prediction result.</p><p>Is there any official step-by-step tutorial, documentation, or example project that explains the complete workflow from:</p><p>BME AI-Studio trained model → deploy on ESP32 or STM32?</p><p>I am mainly looking for a practical guide showing how to move from the Bosch evaluation setup to a custom MCU-based embedded implementation.</p><p>Thank you very much for your support.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Shuttleboard 3.0 which magnetometer]]></title>
            <description><![CDATA[Hello,

I recently ordered the Shuttleboard 3.0 and the Application Board 3.1, but I am unable to retrieve any data from the magnetometer or any other virtual sensor that depends on it (neither via ...]]></description>
            <link>https://community.bosch-sensortec.com/mems-sensors-forum-jrmujtaw/post/shuttleboard-3-0-which-magnetometer-F9u0vXpZ1E5wHj4</link>
            <guid isPermaLink="true">https://community.bosch-sensortec.com/mems-sensors-forum-jrmujtaw/post/shuttleboard-3-0-which-magnetometer-F9u0vXpZ1E5wHj4</guid>
            <category><![CDATA[BMM150]]></category>
            <dc:creator><![CDATA[tire2000]]></dc:creator>
            <pubDate>Mon, 18 May 2026 08:21:47 GMT</pubDate>
            <content:encoded><![CDATA[<p>Hello,</p><p>I recently ordered the Shuttleboard 3.0 and the Application Board 3.1, but I am unable to retrieve any data from the magnetometer or any other virtual sensor that depends on it (neither via COINES with the Sensor API nor via Development Desktop).</p><p>I was wondering if the issue could be that the installed magnetometer is a BMM350, while the firmware I am using is written for the BMM150. Some sources mention the BMM150, but the datasheet specifies a BMM350 magnetometer.</p><p>Could you please clarify which magnetometer is actually installed? If it is the BMM350, is there any firmware available for it? Alternatively, could there be another reason why it is not working at all?</p><p>Best regards</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[FAQs - BME/BSEC]]></title>
            <description><![CDATA[Questions

Type

Answers

 * What is BME680

DS

BME680 is a metal-oxide based chemical sensor. The sensor output is created by interaction of volatile organic compounds (VOCs) with the sensitive layer of BME680. ...]]></description>
            <link>https://community.bosch-sensortec.com/knowledge-base-pg631enp/post/faqs---bme-bsec-aJZ2dLy6u0UasVd</link>
            <guid isPermaLink="true">https://community.bosch-sensortec.com/knowledge-base-pg631enp/post/faqs---bme-bsec-aJZ2dLy6u0UasVd</guid>
            <dc:creator><![CDATA[Fancy]]></dc:creator>
            <pubDate>Fri, 15 May 2026 06:05:11 GMT</pubDate>
            <content:encoded><![CDATA[<table style="width: 1542px" class="confluenceTable tfac-tj tj-rendered tablesorter tablesorter-default stickyTableHeaders"><colgroup><col style="width: 172px"><col style="width: 60px"><col style="width: 1310px"></colgroup><tbody><tr class="tablesorter-headerRow"><th class="relative bg-background border text-left font-bold p-2 [&amp;_p]:m-0" style="width: 172px; min-width: 172px;" rowspan="1" colspan="1"><p><strong>Questions</strong></p></th><th class="relative bg-background border text-left font-bold p-2 [&amp;_p]:m-0" style="width: 60px; min-width: 60px;" rowspan="1" colspan="1"><p><strong>Type</strong></p></th><th class="relative bg-background border text-left font-bold p-2 [&amp;_p]:m-0" style="width: 1310px; min-width: 1310px;" rowspan="1" colspan="1"><p><strong>Answers</strong></p></th></tr><tr class="isolation-auto"><td class="confluenceTd" rowspan="1" colspan="1"><ul><li><p><strong>What is BME680</strong></p></li></ul></td><td class="confluenceTd" rowspan="1" colspan="1"><p><strong>DS</strong></p></td><td class="confluenceTd" rowspan="1" colspan="1"><p>BME680 is a metal-oxide based chemical sensor. The sensor output is created by interaction of volatile organic compounds (VOCs) with the sensitive layer of BME680. As a raw signal, BME680 will output resistance values and its changes due to varying VOC concentrations (the higher the concentration of reducing VOCs, the lower the resistance and vice versa).metal oxide-based sensors such as BME680 can distinguish between reducing (decreasing sensor resistance) and oxidizing (increasing sensor resistance) environments. If strongly oxidizing conditions are present (e.g. chlorine cleaner, nitrous oxides from exhaust gas, higher concentrations of ozone), this may lead to wrong readout of BME since it may output “clean” air in terms of the algorithm where there is none.</p></td></tr><tr class="isolation-auto"><td class="confluenceTd" rowspan="1" colspan="1"><ul><li><p><strong>What is BME688</strong></p></li></ul></td><td class="confluenceTd" rowspan="1" colspan="1"><p><strong>DS</strong></p></td><td class="confluenceTd" rowspan="1" colspan="1"><p>BME688 is the first gas sensor with Artificial Intelligence (AI) and integrated high-linearity and high- accuracy pressure, humidity and temperature sensors. It is housed in a robust yet compact 3.0 x 3.0 x 0.9 mm^3 package and especially developed for mobile &amp; connected applications where size and low power consumption are critical requirements. The gas sensor can detect Volatile Organic Compounds, volatile sulfur compounds and other gases such as carbon monoxide and hydrogen in the part per billion range.&nbsp;</p></td></tr><tr class="isolation-auto"><td class="confluenceTd" rowspan="1" colspan="1"><ul><li><p><strong>What is BME690</strong></p></li></ul></td><td class="confluenceTd" rowspan="1" colspan="1"><p><strong>DS</strong></p></td><td class="confluenceTd" rowspan="1" colspan="1"><p>The BME690 is the gas sensor with Artificial Intelligence (AI) and integrated high-linearity and high-accuracy pressure, humidity and temperature sensors. It is housed in a robust yet compact 3.0 x 3.0 x 0.9 mm³ package and especially developed for mobile &amp; connected applications where size and low power consumption are critical requirements. The BME690 is more robust to previous products and can be used in high condensation applications. The gas sensor can detect Volatile Organic Compounds (VOCs), volatile sulfur compounds (VSCs) and other gases such as carbon monoxide and hydrogen.</p></td></tr><tr class="isolation-auto"><td class="confluenceTd" rowspan="1" colspan="1"><ul><li><p><strong>What’s the difference between BME680 and BME688</strong></p></li></ul></td><td class="confluenceTd" rowspan="1" colspan="1"><p><strong>DS</strong></p></td><td class="confluenceTd" rowspan="1" colspan="1"><p>Additionally to all features of BME680, the BME688 has a gas scanner function. In standard configuration, the presence of VSCs is being detected as indicator for e.g. bacteria growth. And the gas scanner can be customized with respect to sensitivity, selectivity, data rate and power consumption as well, The BME AI-Studio tool enables customers to train the BME688 gas scanner on their specific application, like in home applications, IoT products or Smart Home.</p></td></tr><tr class="isolation-auto"><td class="confluenceTd" rowspan="1" colspan="1"><ul><li><p><strong>What’s the difference between BME688 and BME690</strong></p></li></ul></td><td class="confluenceTd" rowspan="1" colspan="1"><p><strong>DS</strong></p></td><td class="confluenceTd" rowspan="1" colspan="1"><p>Same as BME688, the BME690 has a gas scanner function. In standard configuration, the presence of VSCs is being detected as indicator for e.g. bacteria growth. And the gas scanner can be customized with respect to sensitivity, selectivity, data rate and power consumption as well. The BME AI-Studio tool enables customers to train the BME690 gas scanner on their specific application, like in home appliances, IoT products or Smart Home.</p></td></tr><tr class="isolation-auto"><td class="confluenceTd" rowspan="1" colspan="1"><ul><li><p><strong>BME680, BME688 and BME690 have different impedances</strong></p></li></ul></td><td class="confluenceTd" rowspan="1" colspan="1"><p><strong>DS</strong></p></td><td class="confluenceTd" rowspan="1" colspan="1"><p>Low sensor (BME680) resistance value - selectable range: 178 ~ 12800000 Ohms</p><p>Low sensor (BME680) resistance value - operating range: 2000 ~ 2000000 Ohms</p><p>High sensor (BME688, BME690) resistance value - selectable range: 5865 ~ 102400000 Ohms</p><p>High sensor (BME688, BME690) resistance value - operating range: 100000 ~ 64000000 Ohms</p></td></tr><tr class="isolation-auto"><td class="confluenceTd" rowspan="1" colspan="1"><ul><li><p><strong>Operating temperature for full performance for BME sensors</strong></p></li></ul></td><td class="confluenceTd" rowspan="1" colspan="1"><p><strong>DS</strong></p></td><td class="confluenceTd" rowspan="1" colspan="1"><p>0 ~ 65 ℃</p></td></tr><tr class="isolation-auto"><td class="confluenceTd" rowspan="1" colspan="1"><ul><li><p><strong>Operating temperature ( data read-out possible) for BME sensors</strong></p></li></ul></td><td class="confluenceTd" rowspan="1" colspan="1"><p><strong>DS</strong></p></td><td class="confluenceTd" rowspan="1" colspan="1"><p>-40 ~ 85 ℃</p></td></tr><tr class="isolation-auto"><td class="confluenceTd" rowspan="1" colspan="1"><ul><li><p><strong>What's the difference between selectable range and operating range for BME sensors</strong></p></li></ul></td><td class="confluenceTd" rowspan="1" colspan="1"><p><strong>DS</strong></p></td><td class="confluenceTd" rowspan="1" colspan="1"><p>Selectable range represents all possible values, while operating range represents the values for actual work.</p></td></tr><tr class="isolation-auto"><td class="confluenceTd" rowspan="1" colspan="1"><ul><li><p><strong>Which gases were tested in HQ for BME sensors</strong></p></li></ul></td><td class="confluenceTd" rowspan="1" colspan="1"><p><strong>DS</strong></p></td><td class="confluenceTd" rowspan="1" colspan="1"><p>Here I listed some gases which were measured by HQ, includes min-max concentration.</p><figure data-align="center" data-size="best-fit" data-id="I8othU55ACzzi2xbvYPiX" data-version="v2" data-type="image"><img data-id="I8othU55ACzzi2xbvYPiX" src="https://tribe-eu.imgix.net/I8othU55ACzzi2xbvYPiX?auto=compress,format"></figure></td></tr><tr class="isolation-auto"><td class="confluenceTd" rowspan="1" colspan="1"><ul><li><p><strong>The measured range of raw features about BME sensors</strong></p></li></ul></td><td class="confluenceTd" rowspan="1" colspan="1"><p><strong>DS</strong></p></td><td class="confluenceTd" rowspan="1" colspan="1"><ul><li><p>For BME680:</p></li></ul><p>Temperature: -40 ~ 85 deg C</p><p>Pressure: 30000 ~ 110000 Pa</p><p>Humidity: 0 ~ 100 %</p><p>Gas resistance: 170 ~ 13000000 Ohm (hardware: 178 ~ 12.8e6 Ohm)</p><ul><li><p>For BME688/BME690:</p></li></ul><p>The T/P/H are the same as BME680</p><p>Gas resistance: 5600 ~ 103000000 Ohm (hardware: 5865 ~ 102.4e6 Ohm)</p><ul><li><p>Others Features are same:</p></li></ul><p>IAQ: 0 ~ 500</p><p>Static IAQ: 0 ~ Max</p><p>CO2: 400 ~ Max ppm</p><p>bVOC: 0 ~ 1000 ppm (will be removed from BSEC 3.x)</p></td></tr><tr class="isolation-auto"><td class="confluenceTd" rowspan="1" colspan="1"><ul><li><p><strong>How to evaluate bVoc/CO2 with IAQ?</strong></p></li></ul></td><td class="confluenceTd" rowspan="1" colspan="1"><p><strong>DS</strong></p></td><td class="confluenceTd" rowspan="1" colspan="1"><p>It’s recommended to buy some professional devices as references which can measure bVOC and CO2.</p><p>For CO2: Sometimes you will find there is a little difference between the reference device and BME output, as BME gives an equivalent CO2 output which is calculated based on the S-IAQ, which is not very accurate as the professional devices, but do not say it to the customer directly, we can change some words.</p><p>For bVoc: We can evaluate IAQ by bVOC, here I listed the two charts:</p><p>The first screenshot is for BSEC version 1480 and before versions, which regard IAQ-25 as ‘clean air’. (bVOC = 0.5ppm when the S-IAQ=25, bVOC = 15ppm when the S-IAQ=250)</p><figure data-align="left" data-size="best-fit" data-id="VhiBBDCO6VFHUKVQrvoPd" data-version="v2" data-type="image"><img data-id="VhiBBDCO6VFHUKVQrvoPd" src="https://tribe-eu.imgix.net/VhiBBDCO6VFHUKVQrvoPd?auto=compress,format"></figure><p>The second screenshot is for after BSEC 1480 versions, which regards IAQ-50 as ‘clean air’. (bVOC = 0.5ppm when the S-IAQ=50, bVOC = 15ppm when the S-IAQ=250)</p><figure data-align="left" data-size="best-fit" data-id="T0qIa09vs9ARZtl4eWx04" data-version="v2" data-type="image"><img data-id="T0qIa09vs9ARZtl4eWx04" src="https://tribe-eu.imgix.net/T0qIa09vs9ARZtl4eWx04?auto=compress,format"></figure><p></p><p>Usually bVoc can not indicate the real voc concentration in the environment, what showed it's just a reference to the customer, they can also adjust the relationship between bVoc and IAQ according to their environment.</p><p>In BSEC 3.x version, TVOC equivalent feature will instead of bVoc for BME690.</p></td></tr><tr class="isolation-auto"><td class="confluenceTd" rowspan="1" colspan="1"><ul><li><p><strong>What’s the means by ‘burn-in’ and ‘run-in’? and How long time they will take?</strong></p></li></ul></td><td class="confluenceTd" rowspan="1" colspan="1"><p><strong>DS</strong></p></td><td class="confluenceTd" rowspan="1" colspan="1"><p>‘burn-in’ status means when you get a new sensor, which is a status in the first power-on status, so a sensor only has one ‘burn-in’ status in its life. And in software, we set 0, but it’s recommended to run the sensor for 24h on hardware. Make sure to give the sensor enough time to stabilize.</p><p>‘run-in’ status means a status in each power-on status. In software, we set many time about this status which depends on the power mode, here I listed the relation.</p><table style="width: 240px" class="wrapped confluenceTable"><colgroup><col style="width: 120px"><col style="width: 120px"></colgroup><tbody><tr class="isolation-auto"><td class="confluenceTd" rowspan="1" colspan="1"><p>Power Mode</p></td><td class="confluenceTd" rowspan="1" colspan="1"><p>Run-in time</p></td></tr><tr class="isolation-auto"><td class="confluenceTd" rowspan="1" colspan="1"><p>LP</p></td><td class="confluenceTd" rowspan="1" colspan="1"><p>5min</p></td></tr><tr class="isolation-auto"><td class="confluenceTd" rowspan="1" colspan="1"><p>ULP</p></td><td class="confluenceTd" rowspan="1" colspan="1"><p>20min</p></td></tr><tr class="isolation-auto"><td class="confluenceTd" rowspan="1" colspan="1"><p>CONT</p></td><td class="confluenceTd" rowspan="1" colspan="1"><p>5min</p></td></tr><tr class="isolation-auto"><td class="confluenceTd" rowspan="1" colspan="1"><p>SCAN</p></td><td class="confluenceTd" rowspan="1" colspan="1"><p>1min</p></td></tr><tr class="isolation-auto"><td class="confluenceTd" rowspan="1" colspan="2"><p>And you can observe the output ‘IAQ-accuracy’, it also shows finishing ‘burn-in’status if ‘iaq-accuracy’ changing from 0 to 1.</p></td></tr></tbody></table><p>The fixed 'run-in' time only existed before BSEC 2.5.0.2 version, after that we have run in profiles to speed up the period for BME688 and BME690, why we do that is fixed time will cause some risks about s-t-s deviation.</p><p>However, 'run-in' time is still influenced by the last power-off time, here I list an example of 30mins power-off time for BME690 based on BSEC 3.2.1.0:<br>LP: ~2mins&nbsp; &nbsp;ULP: ~10mins</p></td></tr><tr class="isolation-auto"><td class="confluenceTd" rowspan="1" colspan="1"><ul><li><p><strong>How can I distinguish between Operated Mode and Power Mode?</strong></p></li></ul></td><td class="confluenceTd" rowspan="1" colspan="1"><p><strong>DS</strong></p></td><td class="confluenceTd" rowspan="1" colspan="1"><p>Operated Mode only includes Forced Mode and Parallel Mode, heating is always on in Parallel Mode.</p><p>Power Mode includes LP, ULP, CONT, SCAN(HIGH PERFORMANCE), which determines the frequency at which the sensor outputs the data, so it will also influence the power consumption.</p><p>What’s more, the sensor works in Forced Mode when you set the Power Mode LP, ULP, CONT, and works in Parallel Mode when you set the Power Mode SCAN.</p></td></tr><tr class="isolation-auto"><td class="confluenceTd" rowspan="1" colspan="1"><ul><li><p><strong>Why does my sensor continue to show saturation values during operation?</strong></p></li></ul></td><td class="confluenceTd" rowspan="1" colspan="1"><p><strong>SW</strong></p></td><td class="confluenceTd" rowspan="1" colspan="1"><figure data-align="left" data-size="best-fit" data-id="udb6iD0VTifvo2Ktmk4LM" data-version="v2" data-type="image"><img data-id="udb6iD0VTifvo2Ktmk4LM" src="https://tribe-eu.imgix.net/udb6iD0VTifvo2Ktmk4LM?auto=compress,format"></figure><p>Check which step the sensor at, and check if the temperature and duration of this step are enough or not, it’s recommended to change another Heater Profile to test it again.</p><p>Some old sensors will show the saturation value when the heating temperature is below 150℃.</p></td></tr><tr class="isolation-auto"><td class="confluenceTd" rowspan="1" colspan="1"><ul><li><p><strong>Some customer are using the platforms which aren’t be involved in our generic released package, how can we support them.</strong></p></li></ul></td><td class="confluenceTd" rowspan="1" colspan="1"><p><strong>SW</strong></p></td><td class="confluenceTd" rowspan="1" colspan="1"><p>Contact with AE, and provide the compiler and compilation options.</p></td></tr><tr class="isolation-auto"><td class="confluenceTd" rowspan="1" colspan="1"><ul><li><p><strong>IAQ is abnormal when the customer uses DD2.0 with BME688. (Delete)</strong></p></li></ul></td><td class="confluenceTd" rowspan="1" colspan="1"><p><strong>SW</strong></p></td><td class="confluenceTd" rowspan="1" colspan="1"><p>09/07/2023: Currently DD2.0 can only support BME680 to measure IAQ, which is not suitable for BME688, that means he needs to use EKB to measure IAQ when he wants to use BME688.</p></td></tr><tr class="isolation-auto"><td class="confluenceTd" rowspan="1" colspan="1"><ul><li><p><strong>Temperature and Humidity are incorrect in BSEC mode in DD 2.0</strong></p></li></ul></td><td class="confluenceTd" rowspan="1" colspan="1"><p><strong>SW</strong></p></td><td class="confluenceTd" rowspan="1" colspan="1"><p>The DD tool has a compensation factor hardcoded, this was done as it is persisting since many years ago.</p><p>This is resulting in the BSEC performing a subtraction from the raw temperature/humidity value and providing a compensated temperature/humidity in BSEC mode.</p><p></p><p>&nbsp;</p></td></tr><tr class="isolation-auto"><td class="confluenceTd" rowspan="1" colspan="1"><ul><li><p><strong>Can I set the target temperature and duration? What’re the maximum values</strong></p></li></ul></td><td class="confluenceTd" rowspan="1" colspan="1"><p><strong>SW</strong></p></td><td class="confluenceTd" rowspan="1" colspan="1"><p>Yes, the customer can try their own better heating profiles.</p><p>Maximum value of the target temperature is 400 ℃, and maximum value of the duration is 4032ms.</p></td></tr><tr class="isolation-auto"><td class="confluenceTd" rowspan="1" colspan="1"><ul><li><p><strong>Can I get IAQ without BSEC library?</strong></p></li></ul></td><td class="confluenceTd" rowspan="1" colspan="1"><p><strong>SW</strong></p></td><td class="confluenceTd" rowspan="1" colspan="1"><p>No, you can only get raw data of T/P/H/G without BSEC library, you need to use BSEC library if you want to output IAQ, some compensated values and gas estimation feature.</p></td></tr><tr class="isolation-auto"><td class="confluenceTd" rowspan="1" colspan="1"><ul><li><p><strong>What’s the default temperature for ULP/LP/CONT in the library?</strong></p></li></ul></td><td class="confluenceTd" rowspan="1" colspan="1"><p><strong>SW</strong></p></td><td class="confluenceTd" rowspan="1" colspan="1"><ul><li><p>No setting config file:</p></li></ul><p>BME68X/ULP- Temperature: 400℃, Duration-heater-on: 1943 ms; &nbsp; &nbsp; &nbsp; &nbsp; BME690/ULP- Temperature: 400℃, Duration-heater-on: 1000 ms;</p><p>BME68X/LP- Temperature: 320℃, Duration-heater-on: 197 ms; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;BME690/LP- Temperature: 320℃, Duration-heater-on: 100 ms;</p><p>BME68X/CONT- Temperature: 320℃, Duration-heater-on: 900 ms;&nbsp; &nbsp; &nbsp; &nbsp; BME690/CONT- Temperature: 320℃, Duration-heater-on: 900 ms;</p><ul><li><p>Setting default config file:</p></li></ul><p>BME68X/ULP- Temperature: 400℃, Duration-heater-on: 1943 ms; &nbsp; &nbsp; &nbsp; &nbsp; BME690/ULP- Temperature: 400℃, Duration-heater-on: 1000 ms;</p><p>BME68X/LP- Temperature: 320℃, Duration-heater-on: 197 ms; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;BME690/LP- Temperature: 320℃, Duration-heater-on: 100 ms;</p><p>BME68X/CONT- Temperature: 320℃, Duration-heater-on: 900 ms; &nbsp; &nbsp; &nbsp; &nbsp;BME690/CONT- Temperature: 320℃, Duration-heater-on: 900 ms;</p></td></tr><tr class="isolation-auto"><td class="confluenceTd" rowspan="1" colspan="1"><ul><li><p><strong>Does BSEC2 support BME680?</strong></p></li></ul></td><td class="confluenceTd" rowspan="1" colspan="1"><p><strong>SW</strong></p></td><td class="confluenceTd" rowspan="1" colspan="1"><p>Yes, you can change the subscriptions according to the datasheet.</p></td></tr><tr class="isolation-auto"><td class="confluenceTd" rowspan="1" colspan="1"><ul><li><p><strong>Does BSEC3 support BME680, BME688 and BME690?</strong></p></li></ul></td><td class="confluenceTd" rowspan="1" colspan="1"><p><strong>SW</strong></p></td><td class="confluenceTd" rowspan="1" colspan="1"><p>BSEC 3.x only support both BME688 and BME690, but tvoc equivalent feature only be supported by BME690 in LP Mode, BSEC 3.x can not support BME680.</p></td></tr><tr class="isolation-auto"><td class="confluenceTd" rowspan="1" colspan="1"><ul><li><p><strong>The sensor will show bad performance in low oxygen environment.</strong></p></li></ul></td><td class="confluenceTd" rowspan="1" colspan="1"><p><strong>HW</strong></p></td><td class="confluenceTd" rowspan="1" colspan="1"><p>BME series MOX sensors exhibit abnormal behavior in low-oxygen environments because their operation relies on oxygen molecules in the air forming adsorbed oxygen ions on the sensor surface, which react with target gases in redox reactions to produce changes in resistance. In low-oxygen conditions, the surface oxygen ions are insufficient, limiting the reaction and resulting in reduced sensitivity, delayed response, and even baseline drift.</p></td></tr><tr class="isolation-auto"><td class="confluenceTd" rowspan="1" colspan="1"><ul><li><p><strong>What's the means by .bmeconfig, .config and .aiconfig files in AI_Studio, and how can I use it.</strong></p></li></ul></td><td class="confluenceTd" rowspan="1" colspan="1"><p><strong>SW</strong></p></td><td class="confluenceTd" rowspan="1" colspan="1"><p>The. bmeconfig file is a file that users need to copy to the SD card when collecting data (the board configuration used by EKB), which is the file exported after configuring the BME board using AI_Studio</p><figure data-align="center" data-size="best-fit" data-id="AAGmetaOIknLtEe7P2hAF" data-version="v2" data-type="image"><img data-id="AAGmetaOIknLtEe7P2hAF" src="https://tribe-eu.imgix.net/AAGmetaOIknLtEe7P2hAF?auto=compress,format"></figure><p>The specific content is as follows: (Configure the HP and DC of each sensor on the board)</p><figure data-align="left" data-size="best-fit" data-id="X2H7GL3WLmZCnWN1zZpjV" data-version="v2" data-type="image"><img data-id="X2H7GL3WLmZCnWN1zZpjV" src="https://tribe-eu.imgix.net/X2H7GL3WLmZCnWN1zZpjV?auto=compress,format"></figure><p>The. config and. aiconfig files are automatically generated after collecting data</p><p>. aiconfig means that when users need to connect an EKB board to Mobile AI_Studio, they need to copy it into the SD card</p><p>The things saved in the. config file are similar to the generated. c file array, which can be copied to the SD card along with. aiconfig when using Mobile AI_Studio</p></td></tr><tr class="isolation-auto"><td class="confluenceTd" rowspan="1" colspan="1"><ul><li><p><strong>New Run-in conditioning for LP &amp; ULP mode.</strong></p></li></ul></td><td class="confluenceTd" rowspan="1" colspan="1"><p><strong>DS</strong></p></td><td class="confluenceTd" rowspan="1" colspan="1"><ul><li><p>BME690 in BSEC 3.2.1.0</p></li></ul><figure data-align="center" data-size="best-fit" data-id="jtL2oBA3wbi1m7gKaha4c" data-version="v2" data-type="image"><img data-id="jtL2oBA3wbi1m7gKaha4c" src="https://tribe-eu.imgix.net/jtL2oBA3wbi1m7gKaha4c?auto=compress,format"></figure><ul><li><p>BME688 in BSEC 2.6.1.0 and BSEC 3.2.1.0</p></li></ul><figure data-align="center" data-size="best-fit" data-id="cYogIGR1dmaZQbogaB5My" data-version="v2" data-type="image"><img data-id="cYogIGR1dmaZQbogaB5My" src="https://tribe-eu.imgix.net/cYogIGR1dmaZQbogaB5My?auto=compress,format"></figure></td></tr><tr class="isolation-auto"><td class="confluenceTd" rowspan="1" colspan="1"><ul><li><p><strong>We have handling instructions for BME690.</strong></p></li></ul><p><strong>Are the handling and contamination‑control instructions for BME688 the same or different? Please highlight differences.</strong></p></td><td class="confluenceTd" rowspan="1" colspan="1"><p><strong>HS</strong></p></td><td class="confluenceTd" rowspan="1" colspan="1"><p>With respect to contamination susceptibility and handling risks, BME690 and BME688 are equivalent.</p></td></tr><tr class="isolation-auto"><td class="confluenceTd" rowspan="1" colspan="1"><ul><li><p><strong>What are the potential effects if a BME-series MOX sensor is touched by a human hand during assembly, and are they reversible?</strong></p></li></ul></td><td class="confluenceTd" rowspan="1" colspan="1"><p><strong>HW</strong></p></td><td class="confluenceTd" rowspan="1" colspan="1"><p>Finger Touch &amp; Contamination<br>Two effects:<br>Short‑term, reversible: abnormal readings, response‑time/ noise changes due to residue from fingerprints. These typically recover with time or mild, proper handling.<br>Long‑term, irreversible: chemical poisoning or irreversible adsorption on the sensing layer, causing permanent performance drift.<br>Rule of thumb: prevention over cleaning. Avoid direct touch and keep solvents away from the gas inlet and sensing area whenever possible.</p><p>&nbsp;</p></td></tr><tr class="isolation-auto"><td class="confluenceTd" rowspan="1" colspan="1"><ul><li><p><strong>Is post-assembly cleaning allowed?</strong></p></li><li><p><strong>Which solvents and methods are approved?</strong></p></li><li><p><strong>How should minor fingerprints be handled?</strong></p></li><li><p><strong>Any drying or outgassing guidance?</strong></p></li></ul></td><td class="confluenceTd" rowspan="1" colspan="1"><p><strong>HW</strong></p></td><td class="confluenceTd" rowspan="1" colspan="1"><p>Post-assembly cleaning is allowed only if unavoidable.</p><p>Use ≥90% isopropyl alcohol (IPA) applied lightly with a lint-free wipe or swab. Wipe only the metal cap and its perimeter. Never soak or spray the device, and avoid any liquid entering the gas port.</p><p>For minor fingerprints, prefer passive recovery or clean, dry compressed air instead of using any liquid.</p><p>Ensure the device is completely dry before use to prevent solvent residue.</p></td></tr><tr class="isolation-auto"><td class="confluenceTd" rowspan="1" colspan="1"><ul><li><p><strong>If cleaned with alcohol, does outgassing affect readings for 24–48 h?</strong></p></li><li><p><strong>What quarantining time do you recommend before end‑user use?</strong></p></li><li><p><strong>Our lead time is 5–7 days post‑assembly; is this sufficient?</strong></p></li></ul><p></p></td><td class="confluenceTd" rowspan="1" colspan="1"><p><strong>HW&nbsp;</strong></p></td><td class="confluenceTd" rowspan="1" colspan="1"><p>In low‑VOC conditions, BME688 response time can improve from ~30 s to ~15 s; however, heavy alcohol vapors can prolong recovery and destabilize readings.</p><p>Considering the sensor's ~30 min warm‑up and typical solvent off‑gassing behavior, isolate the device for 8–24 hours in well‑ventilated air after cleaning.</p><p>A 5–7‑day buffer between assembly and shipment normally satisfies this requirement if ventilation is ensured.</p></td></tr><tr class="isolation-auto"><td class="confluenceTd" rowspan="1" colspan="1"><ul><li><p><strong>Which assembly materials are compatible (flux, adhesives, conformal coating)?</strong></p></li><li><p><strong>Are there any “do‑not‑use” chemistries?</strong></p></li><li><p><strong>Any additional precautions for MOX sensors?</strong></p></li></ul></td><td class="confluenceTd" rowspan="1" colspan="1"><p><strong>HW</strong></p></td><td class="confluenceTd" rowspan="1" colspan="1"><p>Use neutral or mildly alkaline fluxes, non-acidic adhesives, and VOC‑low conformal coatings that do not release corrosive byproducts. Avoid materials that can outgas acids, amines, or strong solvents near the sensor.</p><p>Avoid acetic-acid–releasing materials (e.g., acetoxy-cure silicones), strong amines, and other corrosive or reactive compounds. Acetic acid and similar chemicals can corrode or contaminate MOX sensors, leading to degraded performance or permanent damage.</p><p>Always apply adhesives, fluxes, or coatings away from the sensor’s gas port. Ensure proper curing and outgassing before operation. Avoid direct contact or overspray on sensitive surfaces.</p></td></tr><tr class="isolation-auto"><td class="confluenceTd" rowspan="1" colspan="1"><ul><li><p><strong>What is the ESD handling class for BME688?</strong></p></li></ul></td><td class="confluenceTd" rowspan="1" colspan="1"><p><strong>HW</strong></p></td><td class="confluenceTd" rowspan="1" colspan="1"><p>BME688 has an ESD robustness of ±2 kV HBM. Proper ESD precautions should be followed when handling the sensor.</p></td></tr><tr class="isolation-auto"><td class="confluenceTd" rowspan="1" colspan="1"><ul><li><p><strong>What is the Moisture Sensitivity Level (MSL) of BME688?</strong></p></li></ul></td><td class="confluenceTd" rowspan="1" colspan="1"><p><strong>HW</strong></p></td><td class="confluenceTd" rowspan="1" colspan="1"><p>BME688 is MSL 1, meaning it is not moisture-sensitive under standard storage conditions.</p></td></tr><tr class="isolation-auto"><td class="confluenceTd" rowspan="1" colspan="1"><ul><li><p><strong>How should BME688 be stored?</strong></p></li></ul></td><td class="confluenceTd" rowspan="1" colspan="1"><p><strong>HW</strong></p></td><td class="confluenceTd" rowspan="1" colspan="1"><p>Long-term storage is acceptable at ≤30 °C / 85% RH. Prefer a dry, clean, non-corrosive atmosphere. Avoid direct sunlight, high temperature, and high humidity.</p></td></tr><tr class="isolation-auto"><td class="confluenceTd" rowspan="1" colspan="1"><ul><li><p><strong>Is baking required before use?</strong></p></li></ul></td><td class="confluenceTd" rowspan="1" colspan="1"><p><strong>HW</strong></p></td><td class="confluenceTd" rowspan="1" colspan="1"><p>MSL1 parts generally do not require baking. If exposed to high humidity or improper storage, a 125 °C × 24 h bake is a common practice. Always align final bake conditions with the manufacturer’s guidance.</p></td></tr><tr class="isolation-auto"><td class="confluenceTd" rowspan="1" colspan="1"><ul><li><p><strong>Is there a preferred sensor orientation on the PCB?</strong></p></li></ul></td><td class="confluenceTd" rowspan="1" colspan="1"><p><strong>HW</strong></p></td><td class="confluenceTd" rowspan="1" colspan="1"><p>Orient the sensor pins toward the PCB edge or an accessible area for routing and soldering. Ensure the top surface is exposed to ambient air and not shadowed by other components or traces.</p></td></tr><tr class="isolation-auto"><td class="confluenceTd" rowspan="1" colspan="1"><ul><li><p><strong>Are there keep-out areas around the sensor?</strong></p></li></ul></td><td class="confluenceTd" rowspan="1" colspan="1"><p><strong>HW</strong></p></td><td class="confluenceTd" rowspan="1" colspan="1"><p>Keep the sensor away from strong heat sources (power resistors, high-power ICs) and EMI sources (inductors, transformers).</p></td></tr><tr class="isolation-auto"><td class="confluenceTd" rowspan="1" colspan="1"><ul><li><p><strong>How should vent holes be designed?</strong></p></li></ul></td><td class="confluenceTd" rowspan="1" colspan="1"><p><strong>HW</strong></p></td><td class="confluenceTd" rowspan="1" colspan="1"><p>Provide vent holes beneath or around the sensor with a diameter ≥0.5 mm to allow free air exchange.</p></td></tr><tr class="isolation-auto"><td class="confluenceTd" rowspan="1" colspan="1"><ul><li><p><strong>Are there guidelines for airflow channels?</strong></p></li></ul></td><td class="confluenceTd" rowspan="1" colspan="1"><p><strong>HW</strong></p></td><td class="confluenceTd" rowspan="1" colspan="1"><p>Keep ducts as straight as possible. If bends are required, use a radius ≥2× duct height. Add flow guides if needed to distribute airflow uniformly across the sensing area.</p></td></tr><tr class="isolation-auto"><td class="confluenceTd" rowspan="1" colspan="1"><ul><li><p><strong>What is the purpose of burn-in for BME688?</strong></p></li></ul></td><td class="confluenceTd" rowspan="1" colspan="1"><p><strong>HW</strong></p></td><td class="confluenceTd" rowspan="1" colspan="1"><p>The primary purpose of burn-in is to stabilize sensor performance and improve consistency between sensors.</p></td></tr><tr class="isolation-auto"><td class="confluenceTd" rowspan="1" colspan="1"><ul><li><p><strong>What is the semiconductor/chemistry rationale behind burn-in?</strong></p></li></ul></td><td class="confluenceTd" rowspan="1" colspan="1"><p><strong>HW</strong></p></td><td class="confluenceTd" rowspan="1" colspan="1"><p>The MOX element is exposed to high temperature during burn-in to:</p><ol><li><p>Stabilize the microstructure of the metal oxide layer.</p></li><li><p>Stabilize surface states, ensuring consistent adsorption/desorption behavior.</p></li><li><p>Remove impurities and residues from fabrication or handling.</p></li></ol><p>These steps reduce sensor drift, improve reproducibility, and ensure predictable response characteristics.</p></td></tr><tr class="isolation-auto"><td class="confluenceTd" rowspan="1" colspan="1"><ul><li><p><strong>Can burn-in be performed at the factory or at the customer site?</strong></p></li></ul></td><td class="confluenceTd" rowspan="1" colspan="1"><p><strong>HW</strong></p></td><td class="confluenceTd" rowspan="1" colspan="1"><p>Burn-in can be performed in either location.<br>Factory burn-in: Controlled environment allows consistent temperature, clean air, and absence of interfering gases, ensuring uniform sensor stabilization. Risk is minimal if proper procedures are followed.</p><p>Customer-site burn-in: Environment may contain interfering gases (VOC, smoke, chemicals) that can alter sensor surface chemistry, cause drift, or reduce reproducibility. Maintaining consistent temperature and airflow is also more challenging.</p></td></tr><tr class="isolation-auto"><td class="confluenceTd" rowspan="1" colspan="1"><ul><li><p><strong>What precautions are required during burn-in?</strong></p></li></ul></td><td class="confluenceTd" rowspan="1" colspan="1"><p><strong>HW</strong></p></td><td class="confluenceTd" rowspan="1" colspan="1"><p>Ensure the sensor is exposed to clean, interference-free air. Avoid gases or vapors that can adsorb on the MOX surface. Maintain proper temperature and airflow control throughout the burn-in period.</p></td></tr><tr class="isolation-auto"><td class="confluenceTd" rowspan="1" colspan="1"><ul><li><p><strong>How “clean” must the environment be during burn-in?</strong></p></li></ul></td><td class="confluenceTd" rowspan="1" colspan="1"><p><strong>HW</strong></p></td><td class="confluenceTd" rowspan="1" colspan="1"><p>“Clean” means the air should not contain reactive or interfering gases, including tVOCs, silicides, alcohols, carbon monoxide, or other substances that may adsorb on or react with the sensor surface (even unusual compounds such as durian VOCs). Maintain normal indoor temperature and humidity with stable, moderate airflow. The sensor should not be sealed in a small box, as this would prevent proper heat dissipation.</p><p>&nbsp;</p></td></tr><tr class="isolation-auto"><td class="confluenceTd" rowspan="1" colspan="1"><ul><li><p><strong>How can cleanliness be quantified or monitored?</strong></p></li></ul></td><td class="confluenceTd" rowspan="1" colspan="1"><p><strong>HW</strong></p></td><td class="confluenceTd" rowspan="1" colspan="1"><p>While no absolute threshold exists, common practices include:</p><ul><li><p>Measuring TVOC levels with a calibrated sensor; keep as low as practical.</p></li><li><p>Monitoring temperature and relative humidity for stability.</p></li><li><p>Ensuring consistent airflow without stagnant zones.<br>These measures help prevent adsorption of interfering gases and maintain reliable burn-in results.</p></li></ul></td></tr><tr class="isolation-auto"><td class="confluenceTd" rowspan="1" colspan="1"><ul><li><p><strong>What heater temperature/time profiles minimize burn‑in time while ensuring stability?</strong></p></li></ul></td><td class="confluenceTd" rowspan="1" colspan="1"><p><strong>SW</strong></p></td><td class="confluenceTd" rowspan="1" colspan="1"><p>It is necessary to operate the sensor in the same mode.<br>LP mode(IAQ ±15%±15): up to 7 days; qualitative 8 hours;<br>ULP mode(IAQ ±15%±15) up to 15 days; qualitative less than 1day;</p></td></tr><tr class="isolation-auto"><td class="confluenceTd" rowspan="1" colspan="1"><ul><li><p><strong>Is burn‑in required only once for the product life, or after long storage/shock events?</strong></p></li></ul></td><td class="confluenceTd" rowspan="1" colspan="1"><p><strong>HW</strong></p></td><td class="confluenceTd" rowspan="1" colspan="1"><p>Burn‑in/Re‑conditioning<br>On first use, perform ≥8 hours of burn‑in.<br>After prolonged storage or mechanical shock, perform re‑conditioning.<br>Before routine operation, a ~10 min pre‑burn can help stabilize readings.</p></td></tr><tr class="isolation-auto"><td class="confluenceTd" rowspan="1" colspan="1"><ul><li><p><strong>How do we know burn‑in is complete (e.g., ΔR/R stabilization, BSEC state convergence)?</strong></p></li></ul></td><td class="confluenceTd" rowspan="1" colspan="1"><p><strong>HW</strong></p></td><td class="confluenceTd" rowspan="1" colspan="1"><p>It is not always easy to determine when the stabilization is finished from field data, since usually no reproducible pulses occur in real-world condations; thus, aged BME690 sensors were used as reference and completion of stabilization considered to be the time when new and aged sensors behave similar(e.g. ±15% range of IAQ)</p></td></tr><tr class="isolation-auto"><td class="confluenceTd" rowspan="1" colspan="1"><ul><li><p><strong>What unit‑to‑unit resistance variation (pre/post burn‑in) is normal?</strong></p></li></ul></td><td class="confluenceTd" rowspan="1" colspan="1"><p><strong>HW&nbsp;</strong></p></td><td class="confluenceTd" rowspan="1" colspan="1"><p>Resistance Distribution (Indicative)<br>Resistance depends on temperature, humidity, and gas composition. After burn‑in, values stabilize typically in the mega‑ohm to tens‑of‑mega‑ohm range.<br>Under stable lab conditions, a narrower spread such as 20–40 MΩ may be observed. Treat these as guidelines, not hard limits.</p><p>&nbsp;</p></td></tr><tr class="isolation-auto"><td class="confluenceTd" rowspan="1" colspan="1"><ul><li><p><strong>Recommended humidity/temperature and exposure controls during burn‑in to avoid biasing the baseline.</strong></p></li></ul></td><td class="confluenceTd" rowspan="1" colspan="1"><p><strong>HW</strong></p></td><td class="confluenceTd" rowspan="1" colspan="1"><p>Recommended Environment for Burn‑in<br>Humidity: while the measurable range is 0–100% RH, maintain 20–80% RH during burn‑in for stability.<br>Temperature: operating range is −40 to 85 °C; for burn‑in, target ~25 °C to avoid irreversible shifts.</p></td></tr><tr class="isolation-auto"><td class="confluenceTd" rowspan="1" colspan="1"><ul><li><p><strong>Should we use BSEC “gas‑scanner/AI” vs custom heater control? Which BSEC version/configs fit H₂S/NH₃?</strong></p></li></ul></td><td class="confluenceTd" rowspan="1" colspan="1"><p><strong>HW</strong></p></td><td class="confluenceTd" rowspan="1" colspan="1"><p>There is no internal recommended gas configuration. Based on internal experience, HP-354 is more suitable for detecting H2S. AI_Studio supports 16 HP configuration files by default. Customers can select specific profiles based on actual performance or customize their own configuration files.</p></td></tr><tr class="isolation-auto"><td class="confluenceTd" rowspan="1" colspan="1"><ul><li><p><strong>What are the achievable detection limits (LOD), linear/usable ranges for H₂S/NH₃ under the recommended profiles?</strong></p></li></ul></td><td class="confluenceTd" rowspan="1" colspan="1"><p><strong>HW&nbsp;</strong></p></td><td class="confluenceTd" rowspan="1" colspan="1"><p>0.1 ppm ~ 50 ppm NH3<br>100 ppb ~ 500 ppb H2S<br>What we measured in the lab, but it's not the limitation</p><p>&nbsp;</p></td></tr><tr class="isolation-auto"><td class="confluenceTd" rowspan="1" colspan="1"><ul><li><p><strong>How do typical home interferents affect H₂S/NH₃ readings?</strong></p></li><li><p><strong>Is there guidance for compensating for these interferents?</strong></p></li></ul></td><td class="confluenceTd" rowspan="1" colspan="1"><p><strong>HW</strong></p></td><td class="confluenceTd" rowspan="1" colspan="1"><p>Pet excreta, cleaning agents, and food residues may emit sulfur‑ or ammonia‑bearing compounds or VOCs, which can directly skew H₂S/NH₃ and total‑VOC readings.</p><p>Be aware that readings may be biased in the presence of the above interferents. Possible strategies include:</p><ul><li><p>Sensor placement: locate sensors away from direct sources (litter boxes, cleaning areas, kitchens).</p></li><li><p>Data filtering: implement software routines to detect transient spikes associated with known interferents.</p></li><li><p>Calibration updates: periodic recalibration may help reduce long-term drift caused by persistent interfering gases.</p></li></ul></td></tr><tr class="isolation-auto"><td class="confluenceTd" rowspan="1" colspan="1"><ul><li><p><strong>What is the recommended compensation scheme for stable gas readings?</strong></p></li></ul></td><td class="confluenceTd" rowspan="1" colspan="1"><p><strong>HW</strong></p></td><td class="confluenceTd" rowspan="1" colspan="1"><p>A three-layer approach is recommended:</p><ol><li><p>Environmental isolation</p><ul><li><p>Physically shield the sensor from rapid changes in airflow, temperature, or humidity.</p></li></ul></li><li><p>Real-time temperature/humidity correction</p><ul><li><p>Apply real-time compensation using sensor readings of temperature and humidity to correct gas measurement output.</p></li></ul></li><li><p>Dynamic baseline calibration</p><ul><li><p>Combine hardware pre-conditioning and algorithmic optimization to adapt the baseline over time, compensating for drift or environmental effects.</p></li></ul></li></ol><p>This layered approach helps stabilize MOX sensor readings under varying temperature and humidity conditions.</p></td></tr><tr class="isolation-auto"><td class="confluenceTd" rowspan="1" colspan="1"><ul><li><p><strong>How can we diagnose a clogged pinhole in dusty environments?</strong></p></li></ul></td><td class="confluenceTd" rowspan="1" colspan="1"><p><strong>HW</strong></p></td><td class="confluenceTd" rowspan="1" colspan="1"><p>Key telemetry indicators include:</p><ol><li><p>Response time</p><ul><li><p>Slower than a healthy reference by &gt;30% under the same environmental conditions.</p></li></ul></li><li><p>Noise level</p><ul><li><p>Increased to ≥2× normal.</p></li></ul></li><li><p>Baseline drift</p><ul><li><p>Short-term drift exceeding 15% of the post-calibration baseline, with irregular fluctuations.</p></li></ul></li></ol></td></tr><tr class="isolation-auto"><td class="confluenceTd" rowspan="1" colspan="1"><ul><li><p><strong>How should thresholds be used for maintenance decisions?</strong></p></li></ul></td><td class="confluenceTd" rowspan="1" colspan="1"><p><strong>HW</strong></p></td><td class="confluenceTd" rowspan="1" colspan="1"><p>Evaluate response time, noise, baseline drift, and sensitivity decay collectively. When one or more metrics exceed thresholds, maintenance is required. After cleaning or replacement, re-measure these metrics to confirm that performance has returned to acceptable levels.</p></td></tr><tr class="isolation-auto"><td class="confluenceTd" rowspan="1" colspan="1"><ul><li><p><strong>How do different membranes (PTFE/ePTFE, pore size, thickness, oleophobic) affect sensitivity and response time for H₂S/NH₃?</strong></p></li></ul></td><td class="confluenceTd" rowspan="1" colspan="1"><p><strong>HW&nbsp;</strong></p></td><td class="confluenceTd" rowspan="1" colspan="1"><p>Protective membranes generally have a relatively low impact on MOX sensor performance, including response time and recovery time. Minor differences may exist due to thickness or pore structure, but typical PTFE/ePTFE membranes allow gas diffusion sufficient for accurate readings.</p></td></tr><tr class="isolation-auto"><td class="confluenceTd" rowspan="1" colspan="1"><ul><li><p><strong>Are there recommended parts or vendors?</strong></p></li></ul></td><td class="confluenceTd" rowspan="1" colspan="1"><p><strong>HW</strong></p></td><td class="confluenceTd" rowspan="1" colspan="1"><p>Membranes should be chemically inert, mechanically stable, and compatible with H₂S/NH₃ gases. While no specific vendors are required, commercially available PTFE/ePTFE membranes from reputable suppliers are commonly used. Selection should prioritize thickness, pore size, and oleophobic treatment based on application constraints.</p></td></tr><tr class="isolation-auto"><td class="confluenceTd" rowspan="1" colspan="1"><ul><li><p><strong>What behaviors should be expected immediately after minor finger contact?</strong></p></li></ul></td><td class="confluenceTd" rowspan="1" colspan="1"><p><strong>HW&nbsp;</strong></p></td><td class="confluenceTd" rowspan="1" colspan="1"><p>Short-term contact basically does not affect baseline drift, and may only temporarily influence the current reading.</p><p>&nbsp;</p></td></tr><tr class="isolation-auto"><td class="confluenceTd" rowspan="1" colspan="1"><ul><li><p><strong>How should the sensor be restored or cleaned safely?</strong></p></li></ul></td><td class="confluenceTd" rowspan="1" colspan="1"><p><strong>HW</strong></p></td><td class="confluenceTd" rowspan="1" colspan="1"><ul><li><p>Passive recovery: Power off and place in clean air at 30–50% RH for approximately 2 hours.</p></li><li><p>Dry compressed air: Use ≤0.1 MPa, stand 15–20 cm from the gas port at an angle, 3-second blast ×2 with 5-second interval (total ≤6 s).</p></li><li><p>Do NOT use liquids on the gas port. Do not touch the port with swabs or tissue, to avoid fiber shedding.</p></li></ul></td></tr><tr class="isolation-auto"><td class="confluenceTd" rowspan="1" colspan="1"><ul><li><p><strong>Which heat profile is better?</strong></p></li></ul></td><td class="confluenceTd" rowspan="1" colspan="1"><p><strong>SW</strong></p></td><td class="confluenceTd" rowspan="1" colspan="1"><p>Currently, there is no gas-specific heat profile. AI Studio provides 16 preset heat profiles (HPs). Each data collection and training session supports up to 4 HPs. After training, users can check the prediction accuracy for each HP, and the one with the highest accuracy is considered the best-performing heat profile.</p></td></tr><tr class="isolation-auto"><td class="confluenceTd" rowspan="1" colspan="1"><ul><li><p><strong>What is the expected lifetime of BME688 ?</strong></p></li><li><p><strong>How do accelerated stress tests relate to field lifetime?<br></strong></p></li></ul></td><td class="confluenceTd" rowspan="1" colspan="1"><p><strong>HW&nbsp;</strong></p></td><td class="confluenceTd" rowspan="1" colspan="1"><p>Lifetime is estimated based on accelerated storage and stress tests following JEDEC standards.</p><p>Accelerated stress tests such as High-Temperature Operating Life (HTOL) and Temperature Humidity Bias (THB) simulate long-term aging. If BME688 withstands &gt;1,000 hours under these conditions, it is considered equivalent to ~10 years of normal field operation.</p></td></tr><tr class="isolation-auto"><td class="confluenceTd" rowspan="1" colspan="1"><ul><li><p><strong>Is there any way to determine the degree of deterioration of the gas sensor?</strong></p></li><li><p><strong>How to track deterioration over time?</strong></p></li></ul></td><td class="confluenceTd" rowspan="1" colspan="1"><p><strong>HW&nbsp;</strong></p></td><td class="confluenceTd" rowspan="1" colspan="1"><p>Signs of sensor deterioration include:</p><ol><li><p>Decrease in GasRaw value</p><ul><li><p>The baseline GasRaw reading gradually decreases compared to a healthy sensor.</p></li></ul></li><li><p>Slower or reduced IAQ response</p><ul><li><p>IAQ and other derived gas indices rise more slowly and less sharply in response to the same gas concentration.</p></li></ul></li><li><p>Longer recovery time</p><ul><li><p>The time between the rise and fall of IAQ becomes longer, indicating slower sensor kinetics.</p></li></ul></li></ol><p>&nbsp;Maintain time-stamped records of GasRaw, IAQ, and other key sensor outputs under controlled conditions. Analyze trends in baseline, response amplitude, and recovery time to quantify degradation.</p></td></tr><tr class="isolation-auto"><td class="confluenceTd" rowspan="1" colspan="1"><ul><li><p><strong>How can AI Studio differentiate between different gases and their concentrations?</strong></p></li><li><p><strong>What machine learning principle is applied?</strong></p></li></ul><p><strong>&nbsp;</strong></p></td><td class="confluenceTd" rowspan="1" colspan="1"><p><strong>SW&nbsp;</strong></p></td><td class="confluenceTd" rowspan="1" colspan="1"><p>The differentiation relies on unique patterns in the sensor’s gas resistance:</p><ul><li><p>Gas-induced resistance changes</p><ul><li><p>Each gas or concentration produces distinct changes in BME688’s gas resistance, which may not be visible to the naked eye.</p></li></ul></li><li><p>Supervised learning with ground truth</p><ul><li><p>Users provide reference labels (ground truth) corresponding to the gas type and concentration.</p></li></ul></li><li><p>Model training and inference&nbsp;</p><ul><li><p>The AI model maps resistance patterns to the reference labels during training.</p></li><li><p>During testing, if a similar pattern occurs, the model outputs the predicted gas type and/or concentration.</p></li></ul></li></ul><p>This is a supervised machine learning approach, where the model learns to associate sensor signal patterns with labeled gas types/concentrations.</p></td></tr><tr class="isolation-auto"><td class="confluenceTd" rowspan="1" colspan="1"><ul><li><p><strong>For a heat profile with 10 steps per cycle, does AI Studio check the resistance difference between gases (e.g., FA and Ethanol) at each step separately?</strong></p></li><li><p><strong>How does this relate to neural network operation?</strong></p></li></ul></td><td class="confluenceTd" rowspan="1" colspan="1"><p><strong>SW</strong></p></td><td class="confluenceTd" rowspan="1" colspan="1"><p>Not directly. AI Studio uses preprocessing followed by a neural network to analyze the data. The neural network can extract any relevant information from the 10 heater steps, including:</p><ul><li><p>Differences between gases</p></li><li><p>Mean, variance, or other statistical features</p></li><li><p>Any patterns that map gas resistance to the reference label</p></li></ul><p>It does not require step-by-step manual comparison; the network automatically learns the features needed for classification or regression.</p><p>Neural networks can learn complex mappings between input signals (heater step resistance) and outputs (gas type/concentration) from labeled data. You can refer to standard resources on how neural networks process multivariate time-series inputs for further understanding.</p></td></tr><tr class="isolation-auto"><td class="confluenceTd" rowspan="1" colspan="1"><ul><li><p><strong>How does AI Studio use variance in each heat profile step to differentiate gases and concentrations?</strong></p></li><li><p><strong>How should rapid transitions between gases be handled?</strong></p></li><li><p><strong>Can slow transitions be used for training?</strong></p></li></ul><p><strong>&nbsp;</strong></p></td><td class="confluenceTd" rowspan="1" colspan="1"><p><strong>SW</strong></p></td><td class="confluenceTd" rowspan="1" colspan="1"><p>The term “variance per step” usually refers to the signal fluctuations during a heat step. To distinguish different gases or ppm levels, there must be a measurable change in gas resistance.<br>If the gas changes quickly (fast transition in resistance), it is recommended not to use this period for training. The sensor may not detect the new gas immediately, but the model will detect it after the sensor stabilizes. This approach improves overall model performance.<br>Yes, if the resistance change from one gas to another occurs slowly, this period can be included for training. The model may detect gas changes more quickly, but it may also produce occasional false outputs after stabilization. This trades overall stability for faster response.</p></td></tr><tr class="isolation-auto"><td class="confluenceTd" rowspan="1" colspan="1"><ul><li><p><strong>What is the minimal quantity of sensors recommended for gas training?</strong></p></li><li><p><strong>Any additional recommendations for sensor usage?</strong></p></li></ul></td><td class="confluenceTd" rowspan="1" colspan="1"><p><strong>SW</strong></p></td><td class="confluenceTd" rowspan="1" colspan="1"><p>Ideally, use as many sensors as possible within budget. With Bosch development kit boards, 2 boards provide 16 sensors, which is the minimum recommended number. If performance is insufficient, increase the number of sensors.</p><ul><li><p>Use brand-new sensors that have completed burn-in.</p></li><li><p>Enable data augmentation in BME AI Studio to improve model robustness.</p></li></ul></td></tr><tr class="isolation-auto"><td class="confluenceTd" rowspan="1" colspan="1"><ul><li><p><strong>Can burn-in time be decreased by higher temperature or shorter duration?</strong></p></li></ul><p><strong>&nbsp;</strong></p></td><td class="confluenceTd" rowspan="1" colspan="1"><p><strong>SW</strong></p></td><td class="confluenceTd" rowspan="1" colspan="1"><p>his is an open topic that has not yet been explored or verified for BME688. In general, higher temperature and longer heater-on time are conventionally used to reduce burn-in for MOX sensors, but no validated data exists for BME688 yet.<br></p><p>&nbsp;</p></td></tr><tr class="isolation-auto"><td class="confluenceTd" rowspan="1" colspan="1"><ul><li><p><strong>ISO16000-29 'Test methods for VOC detectors'&nbsp; document link</strong></p></li></ul></td><td class="confluenceTd" rowspan="1" colspan="1"><p><strong>DS</strong></p></td><td class="confluenceTd" rowspan="1" colspan="1"><p><a class="text-interactive hover:text-interactive-hovered" rel="noopener noreferrer nofollow" href="https://bosch.sharepoint.com/:b:/r/sites/msteams_9b4904-BSTESA4/Shared%20Documents/BST%20ESA4/BEEM%20Team/BME%20Topics/OPPO%20BME688/EN_ISO_16000-29_2014-06.pdf?csf=1&amp;web=1&amp;e=JHAXT0">EN_ISO_16000-29_2014-06.pdf</a>.</p></td></tr><tr class="isolation-auto"><td class="confluenceTd" rowspan="1" colspan="1"><ul><li><p><strong>What is manual calibration for TVOC equivalent in BSEC 3.2.1.0?</strong></p></li></ul></td><td class="confluenceTd" rowspan="1" colspan="1"><p><strong>SW</strong></p></td><td class="confluenceTd" rowspan="1" colspan="1"><p>In BSEC 3.2.1.0, the TVOC equivalent is by default calibrated to lab data without considering interfering gases. In real-world environments, other gases may affect readings, so the manual calibration API was provided. Users could:</p><ol><li><p>Enable the API.</p></li><li><p>Calibrate TVOC to a reference concentration (e.g., 250 ppb) in the expected environment.</p></li><li><p>Disable the API to prevent deviation from the calibrated value.</p></li></ol><p>Since TVOC (manual calibration) and IAQ (automatic calibration) are calibrated separately, differences between reported values could occur.</p><p>In BSEC 3.3.0, TVOC calibration was changed to automatic calibration, removing the need for a separate manual calibration step. This aligns TVOC calibration more closely with IAQ and reduces discrepancies between the two outputs.</p></td></tr><tr class="isolation-auto"><td class="confluenceTd" rowspan="1" colspan="1"><ul><li><p><strong>Do we have any docs for quick calibration and slow calibration in TVOC feature in this release, and how long it will take to get the reliable output and the lowest s-t-s deviation output.&nbsp;</strong></p></li></ul></td><td class="confluenceTd" rowspan="1" colspan="1"><p><strong>SW</strong></p></td><td class="confluenceTd" rowspan="1" colspan="1"><p>The recommendation to customer is 22 days in field. By this time, TVOC would be calibrated and S2S would be least. We are not giving specific instructions for quick calibration as it is for development purpose.</p></td></tr><tr class="isolation-auto"><td class="confluenceTd" rowspan="1" colspan="1"><ul><li><p><strong>Conditions that trigger a BSEC -2 error in the BSEC built-in algorithm</strong></p></li></ul></td><td class="confluenceTd" rowspan="1" colspan="1"><p><strong>SW</strong></p></td><td class="confluenceTd" rowspan="1" colspan="1"><p>The BSEC -2 error is triggered when one or more BME sensor input parameters exceed the allowable input limits specified by the BSEC algorithm.</p><ul><li><p>(gas): High: 170.0 ~ 1.03E+8&nbsp; Low: 170.0 ~ 1.32E+7</p></li><li><p>(temperature): -65.0 ~ 125.0</p></li><li><p>(humidity): 0.0 ~ 100.0</p></li><li><p>(pressure): 0.0 ~ 2.0E+6</p></li></ul><p></p></td></tr><tr class="isolation-auto"><td class="confluenceTd" rowspan="1" colspan="1"><ul><li><p><strong>Can we use the current PCB designed for the BME680/BME688 and upgrade it with the BME690 without any hardware changes?</strong></p></li></ul></td><td class="confluenceTd" rowspan="1" colspan="1"><p><strong>HW</strong></p></td><td class="confluenceTd" rowspan="1" colspan="1"><p>Yes, the BME690 is designed to be backward compatible with existing PCB layouts developed for the BME680 and BME688. In most cases, the BME690 can be mounted directly onto the existing hardware without requiring PCB modifications.</p><p>However, it is recommended to update to the latest software API version to ensure full support of the BME690 features and optimized signal processing. The updated API automatically detects the connected sensor variant and applies the appropriate configuration and compensation algorithms.</p></td></tr><tr class="isolation-auto"><td class="confluenceTd" rowspan="1" colspan="1"><ul><li><p><strong>Is it necessary to actively force air into the BME sensors when taking measurements?</strong></p></li></ul><p></p><p><strong><br></strong></p></td><td class="confluenceTd" rowspan="1" colspan="1"><p><strong>DS</strong></p></td><td class="confluenceTd" rowspan="1" colspan="1"><p>No, active airflow is generally not required. Gas exchange occurs naturally through diffusion. Whenever the gas composition around the BME sensor changes, a concentration gradient is created, causing gases to diffuse into and out of the sensor package.</p><p>Due to the compact sensor design and the very short distance between the package opening and the gas sensing element, the sensor responds to environmental gas changes within a few seconds under typical operating conditions.</p></td></tr><tr class="isolation-auto"><td class="confluenceTd" rowspan="1" colspan="1"><ul><li><p><strong>How many measurements can be stored on the BME sensors?</strong></p></li></ul></td><td class="confluenceTd" rowspan="1" colspan="1"><p><strong>DS</strong></p></td><td class="confluenceTd" rowspan="1" colspan="1"><p>The BME sensor stores configuration information such as scan profiles, along with a limited amount of temporary measurement data in its internal buffer. In normal operation, the measurement data is continuously read out by the host microcontroller (MCU) connected to the sensor.</p><p>As a result, the practical storage capacity mainly depends on the available memory of the host system rather than the sensor itself. When using the Bosch sensor software library on the MCU, sensor data can be processed directly on the device, reducing the need to store large amounts of raw measurement data. In many applications, storing only the relevant processed output values is sufficient.</p></td></tr><tr class="isolation-auto"><td class="confluenceTd" rowspan="1" colspan="1"><ul><li><p><strong>How much computing power is required to run the AI software? Can you provide examples of compatible MCUs?</strong></p></li></ul></td><td class="confluenceTd" rowspan="1" colspan="1"><p><strong>SW</strong></p></td><td class="confluenceTd" rowspan="1" colspan="1"><p>Training and optimizing AI models using Bosch AI-Studio requires a desktop or laptop computer with sufficient processing resources for data analysis and algorithm generation.</p><p>However, executing a trained algorithm on an embedded device requires only modest computing resources. Many commonly used microcontrollers are capable of running the sensor processing and AI inference in real time. Examples include the ESP8266, ESP32, and a wide range of ARM Cortex-M based MCUs.</p><p>The exact hardware requirements depend on the complexity of the application, sampling configuration, and system-level software architecture.</p></td></tr><tr class="isolation-auto"><td class="confluenceTd" rowspan="1" colspan="1"><ul><li><p><strong>Can you please explain how the gas scanning functionality works?</strong></p></li></ul></td><td class="confluenceTd" rowspan="1" colspan="1"><p><strong>SW</strong></p></td><td class="confluenceTd" rowspan="1" colspan="1"><p>The BME gas sensor performs measurements under multiple operating conditions during a gas scan sequence. This is achieved by dynamically controlling internal sensor parameters, such as the heater temperature profile, which changes the sensor sensitivity to different gases and volatile compounds over time.</p><p>By combining the measurement responses from these different operating points, the sensor can generate characteristic signal patterns — often referred to as “fingerprints” — for specific gas mixtures or environmental conditions.</p><p>Using Bosch AI-Studio, developers can configure, optimize, and train custom scan profiles for their specific application requirements. This allows the system to improve selectivity and adapt the sensing behavior for use cases such as air quality monitoring, odor classification, or gas detection.</p></td></tr><tr class="isolation-auto"><td class="confluenceTd" rowspan="1" colspan="1"><ul><li><p><strong>Does the BME sensor include integrated Flash or EEPROM memory?</strong></p></li></ul></td><td class="confluenceTd" rowspan="1" colspan="1"><p><strong>SW</strong></p></td><td class="confluenceTd" rowspan="1" colspan="1"><p>No. The BME sensor does not contain integrated Flash or EEPROM memory for long-term user data storage. Configuration data and measurement results are typically managed by the external host microcontroller (MCU) connected to the sensor.</p></td></tr><tr class="isolation-auto"><td class="confluenceTd" rowspan="1" colspan="1"><ul><li><p><strong>After training an algorithm using data collected from multiple sensors, can the resulting model be deployed on a device using only a single BME sensor?</strong></p></li></ul></td><td class="confluenceTd" rowspan="1" colspan="1"><p><strong>SW</strong></p></td><td class="confluenceTd" rowspan="1" colspan="1"><p>Yes. Bosch AI-Studio can export the trained algorithm as a configuration file or configuration string that can be integrated into the Bosch sensor software running on a target device with a single BME690 sensor.</p><p>Once deployed, the device can locally execute the trained model and directly evaluate the gas scan data generated by the BME690 in real time. This enables compact and cost-efficient implementations without requiring multiple sensors during normal operation.</p><p>However, the achievable performance and robustness of the trained model may depend on factors such as sensor variation, environmental conditions, and the quality and diversity of the training data.</p></td></tr><tr class="isolation-auto"><td class="confluenceTd" rowspan="1" colspan="1"><ul><li><p><strong>Which AI or neural network topology is used? Is the system based on neural networks or statistical pattern recognition?</strong></p></li></ul></td><td class="confluenceTd" rowspan="1" colspan="1"><p><strong>SW</strong></p></td><td class="confluenceTd" rowspan="1" colspan="1"><p>The current version of Bosch AI-Studio uses a neural network–based approach for gas pattern recognition. The software utilizes a predefined neural network architecture together with configurable training parameters and optimization methods, including the ADAM optimizer, for model training.</p><p>The generated models are designed to operate efficiently on embedded systems with limited computational resources while still enabling reliable classification of gas patterns and environmental conditions.</p><p>In addition, we explicitly encourages customers to develop and implement their own algorithms based on their specific application requirements. AI-Studio is designed as a flexible development tool that supports customization of models and workflows to enable application-specific optimization.</p></td></tr><tr class="isolation-auto"><td class="confluenceTd" rowspan="1" colspan="1"><ul><li><p><strong>Is it possible to detect gases produced by burning network cables or electronic components?</strong></p></li></ul></td><td class="confluenceTd" rowspan="1" colspan="1"><p><strong>DS</strong></p></td><td class="confluenceTd" rowspan="1" colspan="1"><p>Yes, this can be a relevant application for the BME690. In scenarios where abnormal conditions occur in electrical systems or cabinets, gas emissions can often be an early indicator of faults or overheating.</p><p>Typically, two main situations can be distinguished:</p><ol><li><p><strong>Overheating or material degradation</strong><br>When insulation materials or other components are exposed to excessive heat or short circuits, they may begin to decompose or melt. This process leads to increased outgassing, often containing a mixture of volatile organic compounds (VOCs), including unburned hydrocarbons. These gas signatures can be detected by the BME sensor in a manner similar to how humans perceive odor.</p></li><li><p><strong>Electrical arcing or flashovers</strong><br>In cases of high voltage events, short circuits, or arcing, ozone (O₃) and other reactive gases can be generated. These have a distinct gas signature compared to thermal decomposition products and can also be detected by the BME sensor.</p></li></ol><p>By analyzing these different gas patterns using appropriate algorithms, the sensor can potentially contribute to early detection of electrical faults and abnormal operating conditions.</p></td></tr><tr class="isolation-auto"><td class="confluenceTd" rowspan="1" colspan="1"><ul><li><p><strong>Does the BME sensor detect combustible gases such as methane (CH₄) and propane (C₃H₈), as well as toxic gases like carbon monoxide (CO)?</strong></p></li></ul></td><td class="confluenceTd" rowspan="1" colspan="1"><p><strong>DS</strong></p></td><td class="confluenceTd" rowspan="1" colspan="1"><p>The BME sensor is sensitive to a broad range of gases, including many volatile organic compounds (VOCs) and various combustible and reducing gases. This includes many hydrocarbons (CₓHᵧ) and gases such as carbon monoxide (CO), which can be reflected in the overall gas pattern measured by the sensor.</p><p>Combustible gases are often categorized into methane (CH₄) and non-methane organic gases (NMOG). Methane is a special case, as it is chemically less reactive and typically requires specific sensing materials or catalysts for strong direct response. As a result, the BME sensor is not optimized for strong direct sensitivity to methane, and detection performance for methane alone may be limited, especially at lower concentrations.</p><p>However, in many real-world applications, methane is not present in isolation but occurs alongside other gases such as VOCs or sulfur-containing compounds, which the BME sensor can detect effectively. In such scenarios, gas mixture patterns can still provide useful information for classification and anomaly detection when combined with appropriate algorithms.</p><p>For application-specific evaluation, testing the sensor under real operating conditions is recommended to determine suitability and achievable performance.</p></td></tr><tr class="isolation-auto"><td class="confluenceTd" rowspan="1" colspan="1"><ul><li><p><strong>Is the BME sensor certified as a medical sensor?</strong></p></li></ul></td><td class="confluenceTd" rowspan="1" colspan="1"><p><strong>DS</strong></p></td><td class="confluenceTd" rowspan="1" colspan="1"><p>No. The BME sensor is not certified as a medical sensor at the component level. Sensor components are typically qualified according to standards applicable to consumer electronics, such as JEDEC requirements, rather than medical device regulations.</p><p>Medical certification, where required, is carried out at the device or system level by the manufacturer of the final product, as certification depends on the complete system design, intended use, and regulatory classification.</p><p>In general, customers are responsible for evaluating and ensuring compliance of their end products within the relevant application domain and regulatory framework. From a system perspective, the benefit of pre-certified individual sensor components is therefore limited in most cases.</p></td></tr><tr class="isolation-auto"><td class="confluenceTd" rowspan="1" colspan="1"><ul><li><p><strong>Is it possible to detect drugs or explosive materials using the BME sensor?</strong></p></li></ul></td><td class="confluenceTd" rowspan="1" colspan="1"><p><strong>DS</strong></p></td><td class="confluenceTd" rowspan="1" colspan="1"><p>Bosch Sensortec does not provide validated use cases or application experience for the detection of drugs or explosive materials with the BME sensor. The sensor is designed for general gas sensing applications and the detection of volatile gas patterns in air quality and environmental monitoring contexts.</p><p>In principle, the BME sensor can measure changes in gas composition, and its response to different volatile compounds can be evaluated in customer-specific development and testing environments. However, Bosch does not provide performance specifications, calibration data, or application guidance for drug or explosive detection use cases.</p><p>Customers may conduct their own evaluation using development hardware to determine suitability for their specific application, subject to applicable laws and regulations.</p></td></tr><tr class="isolation-auto"><td class="confluenceTd" rowspan="1" colspan="1"><ul><li><p><strong>How can I determine whether the gases in my application can be measured with the BME sensor?</strong></p></li></ul></td><td class="confluenceTd" rowspan="1" colspan="1"><p><strong>DS</strong></p></td><td class="confluenceTd" rowspan="1" colspan="1"><p>A key purpose of Bosch AI-Studio is to enable exactly this type of evaluation in real-world conditions. Instead of requiring detailed prior knowledge about individual target gases or their concentrations, developers can directly test the sensor in their actual application environment.</p><p>Traditionally, gas sensing development required extensive laboratory testing with individual gases in controlled environments, such as synthetic air. While such tests can provide useful baseline information, they often do not fully represent real-world conditions, where multiple gases and environmental influences are present simultaneously.</p><p>With the BME sensors and Bosch AI-Studio, developers can collect data directly in the target application, build and evaluate models under real operating conditions, and iteratively optimize performance based on real-world gas mixtures and dynamics. This approach helps bridge the gap between laboratory characterization and practical field performance.</p></td></tr><tr class="isolation-auto"><td class="confluenceTd" rowspan="1" colspan="1"><ul><li><p><strong>Are over-the-air (OTA) updates possible to enable detection of additional gases or substances in the future?</strong></p></li></ul></td><td class="confluenceTd" rowspan="1" colspan="1"><p><strong>SW</strong></p></td><td class="confluenceTd" rowspan="1" colspan="1"><p>Yes. The system supports updating sensor behavior through software-based configuration. The sensor’s measurement behavior is defined by software parameters rather than being permanently fixed in hardware.</p><p>When using Bosch AI-Studio, a trained application results in a configuration package (including model parameters and scan profile settings). This package can be deployed to field devices via over-the-air update mechanisms, as it is typically small in size and designed for efficient transfer.</p><p>Once the updated configuration is loaded into the Bosch sensor software on the device, the BME sensor operates according to the new scan profile and model behavior, enabling adaptation to new application requirements without requiring hardware changes.</p></td></tr><tr class="isolation-auto"><td class="confluenceTd" rowspan="1" colspan="1"><ul><li><p><strong>Why does the evaluation board use eight sensors?</strong></p></li></ul></td><td class="confluenceTd" rowspan="1" colspan="1"><p><strong>HW</strong></p></td><td class="confluenceTd" rowspan="1" colspan="1"><p>The development kit is designed to support flexible evaluation and optimization using Bosch AI-Studio. It allows developers to fine-tune key parameters such as performance, output data rate (ODR), and power consumption according to application-specific requirements.</p><p>By integrating eight BME sensors on a single evaluation board, the system enables parallel testing of multiple configurations under identical environmental conditions. This allows developers to compare different settings simultaneously, improving data quality and statistical reliability while significantly reducing overall development time.</p></td></tr></tbody></table>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What is the mass and SNR of the BMA580 accelerometer?]]></title>
            <description><![CDATA[I looked through the data sheet for the BMA580, and can't find the unit's mass or SNR. Could someone supply these?]]></description>
            <link>https://community.bosch-sensortec.com/mems-sensors-forum-jrmujtaw/post/what-is-the-mass-and-snr-of-the-bma580-accelerometer-MTt7ORJ1JyUyFYQ</link>
            <guid isPermaLink="true">https://community.bosch-sensortec.com/mems-sensors-forum-jrmujtaw/post/what-is-the-mass-and-snr-of-the-bma580-accelerometer-MTt7ORJ1JyUyFYQ</guid>
            <category><![CDATA[BMA580]]></category>
            <dc:creator><![CDATA[m-ga]]></dc:creator>
            <pubDate>Wed, 13 May 2026 18:55:48 GMT</pubDate>
            <content:encoded><![CDATA[<p>I looked through the data sheet for the BMA580, and can't find the unit's mass or SNR. Could someone supply these?</p>]]></content:encoded>
        </item>
    </channel>
</rss>