Bosch Sensortec Community

    cancel
    Showing results for 
    Search instead for 
    Did you mean: 
    SOLVED

    Development Desktop 2.0 consuming a lot of CPU

    Development Desktop 2.0 consuming a lot of CPU

    raktas
    New Poster

    Hello! I am trying to log the sensor data using BMI090L from the accelerometer and the gyroscope. Within one system, we have some other hardware that we need to run with the BMI090L at the same time. Recently I noticed that the Development Desktop software is comsuming a lot of CPU only for running, not for logging the data. This is blocking to use the other components of my system by allocating too much space on the buffer or the memory, but I am not fully sure what, because I don't really know how this software is implemented. I have checked other possibilities for data logging in a huma readable format, which is what I need. I saw there are possibilities to use the COINES or the UI for the Development Desktop, but in both options, further  programming tasks are needed but I believe Development Desktop is already capaple of what I really need and using the UI would be redundant work for me.

    Is there a way to allocate the resources of the software in a more reasonable way? Because I really don't know why the software itself is allocating %15 of CPU utilization only because I opened the software. My PC is a strong one with Intel(R) Core (TM) i7-3770 CPU @ 3.40GHz with 16GB ram installed.

    Many thanks for your helps in advance. I wish you a nice day.

    Kindest regards,
    Rozerin.

    1 REPLY 1

    FAE_CA1
    Community Moderator
    Community Moderator

    Hi,

    Thanks for your inquiry.

    Development Desktop 2.0 (DD2.0) GUI SW uses polling mode for data logging into a txt or csv file. After you finish configuring BMI090L accel and gyro power mode, output data rate (ODR) and full scale ranges, DD2.0 will keep polling the data ready bit from the accel and gyro status registers respectively. If that new data bit is set, then DD2.0 will read BMI090L data registers and store the data in the file.

    For example, if you set accel and gyro to 100Hz both, then the data log file will have both data at each time interval of 10ms. If you set accel to 100Hz ODR and gyro to 200Hz ODR, then gyro data will be stored in the file at 5ms interval while accel data 10ms interval.

    You can use COINES SW to log data into file by yourself.

    Thanks.

    Icon--AD-black-48x48Icon--address-consumer-data-black-48x48Icon--appointment-black-48x48Icon--back-left-black-48x48Icon--calendar-black-48x48Icon--center-alignedIcon--Checkbox-checkIcon--clock-black-48x48Icon--close-black-48x48Icon--compare-black-48x48Icon--confirmation-black-48x48Icon--dealer-details-black-48x48Icon--delete-black-48x48Icon--delivery-black-48x48Icon--down-black-48x48Icon--download-black-48x48Ic-OverlayAlertIcon--externallink-black-48x48Icon-Filledforward-right_adjustedIcon--grid-view-black-48x48IC_gd_Check-Circle170821_Icons_Community170823_Bosch_Icons170823_Bosch_Icons170821_Icons_CommunityIC-logout170821_Icons_Community170825_Bosch_Icons170821_Icons_CommunityIC-shopping-cart2170821_Icons_CommunityIC-upIC_UserIcon--imageIcon--info-i-black-48x48Icon--left-alignedIcon--Less-minimize-black-48x48Icon-FilledIcon--List-Check-grennIcon--List-Check-blackIcon--List-Cross-blackIcon--list-view-mobile-black-48x48Icon--list-view-black-48x48Icon--More-Maximize-black-48x48Icon--my-product-black-48x48Icon--newsletter-black-48x48Icon--payment-black-48x48Icon--print-black-48x48Icon--promotion-black-48x48Icon--registration-black-48x48Icon--Reset-black-48x48Icon--right-alignedshare-circle1Icon--share-black-48x48Icon--shopping-bag-black-48x48Icon-shopping-cartIcon--start-play-black-48x48Icon--store-locator-black-48x48Ic-OverlayAlertIcon--summary-black-48x48tumblrIcon-FilledvineIc-OverlayAlertwhishlist