FAQ
Here are frequently asked questions (FAQ) from our customers:
The recorded time stamp does not match with the actual time in which the data was collected. How to correct the RTC?
Answer: Connect to the BME AI-Studio Mobile App for automatic time syncing. Please ensure that a coin cell is inserted for continuous timekeeping. Please also refer to a few things to keep in mind. Additionally, please note that this is applicable only for BME688 Development kit. The BME690 shuttle board uses the Application board 3.1 in which the RTC module is not available, so time stamps are not included in filenames or logs.
How to select the right heater profile for detecting my target application?
Answer: Selecting the ideal heater profile requires evaluating the performance on various options. We suggest starting with the Default configuration, which generally yields favorable results across many use cases and then move on to explore the right Heater Profile and Duty Cycle As a next step the right Heater Profile for the use case can be explored.
How can I use the trained algorithm (configuration file) in my device with one BME688 or BME690 sensor?
Answer: Once the algorithm is trained, please export the generated .c and .h files which can be used along with the BSEC library in the host MCU. See the respective sections on how to export a BSEC configuration file and on how to use custom hardware.
Which version of BSEC is compatible to the BME AI-Studio versions?
Answer: The BSEC compatibilty to BME AI-Studio versions is available here. We recommend upgrading to the latest version for accessing the new features.
How to generate and deploy the config file from the BME AI-Studio?
Answer: Once the algorithm is trained, the configuration file can be exported by clicking on the Export for BSEC in the “Training Results” tab in the BME AI-Studio Desktop. It contains 5 file formats. The file with .config, .c, .h and .csv contains the same information and can be selected by the customer based on their platform requirements whereas the .config and .aiconfig file can be used in the BME688 or BME690 development kit for live testing the trained algorithm with the BME AI-Studio Mobile App.
What are the system requirements to execute the BME-AI-Studio?
Answer: We have tested the BME AI-Studio on the following system configurations and we recommend this or newer configurations for the most optimal performance.
Can I connect multiple BME sensors using one MCU and BSEC library?
Answer: The BSEC 2.4.0.0 and later versions support “Multi instance interface support” and the user can use multiple BME sensors with a single BSEC library installed on the host MCU. Please refer to this example code.
Can I use a custom Heater Profile for my use case/application?
Answer: Presently only the 16 Heater Profiles listed in the BME AI-Studio are supported. Each defined Heater Profile is unique and sufficient for a wide range of applications.
Is there any example code available which provides support to deploy my use case?
Answer: Yes, the bsec_iot_example is included with the BSEC release package. This example code, written in C, demonstrates how to integrate the BSEC algorithm on a custom hardware. The example code for BME688 and BME690 development kits are available in the “examples” folder of BSEC release package.
Why the BME AI-Studio Desktop Linux and Mac packages are no more available in the Bosch Sensortec Website for download?
Answer: In the past years, we have noted that BME AI-Studio Windows version is the most popular and preferred platform among users. So to optimize maintainability and ensure faster releases of Software, we have decided to continue with the Windows version only.
Why the BME AI-Studio Server packages is no more available in the Bosch Sensortec Website for download?
Answer: Both the BME AI Studio Desktop and Server has the same backend AI engine but the key difference is that the BME AI Studio Server do not have the frontend User Interface and mainly works based on API’s to automate the data collection and training process. It has been noted that the user needs advanced IT expertise to operate the BME AI Studio Server version compared to the Desktop version. Whereas the BME AI Studio Desktop version can cater to all the training and testing required with an easy step to operate User Interface. So to optimize maintainability and ensure faster releases of Software, we have decided to discontinue the BME AI Studio Server version.
What gases can the BME sensor detect?
Answer: The BME sensor has been qualified to detect the total VOC content inside an Indoor environment and provide the IAQ index as a standard plug and play function. Regarding specific gases Bosch Sensortec has additionally tested the BME sensor to hydrogen sulfide (H2S), ethanol (EtOH) and carbon monoxide (CO) to which the sensor is selective to. The BME sensor is a Metal Oxide sensor and it reacts/responds to a variety of oxidizing and reducing gases, in case the user wants to test it with other gases we encourage to test the BME sensor based on the specific application and use case requirements before coming to a conclusion.
Why there are two different BME690 shuttle boards available and which software are compatible to it?
Answer: For the BME690 two different Shuttle boards are available
- BME690 1x Shuttle board
- BME690 8x Shuttle board
Both of these shuttle boards have different purpose and works with a set of software ecosystem. The overview is as follows:
| # | Hardware | Compatible Software | Comments |
|---|---|---|---|
| 1. | BME690 1x shuttle board + Application Board 3.1 | Development Desktop Software | Ideally to test and demonstrate the IAQ features |
| 2. | BME690 8x shuttle board + Application Board 3.1 | BME690 Development kit Software + BME AI Studio Software | To train and test the sensor for specific use case development |
So, the BME690 8x shuttle is compatible only with BME690 Development kit Software + BME AI Studio Software and not with Development Desktop Software (Development Desktop is compatible with BME690 1x shuttle board only). Also please check the compatible software versions for the ecosystem to work seamlessly.