Bosch Sensortec Community

    cancel
    Showing results for 
    Search instead for 
    Did you mean: 

    BHI260AB get calibration profile error

    BHI260AB get calibration profile error

    hjoungjoo
    New Poster
    Hello, I made a product with BHI260AB.
    My product specifications are as follows.
     
    1. Use BHI260AB and AK09915.
    2. The direction of the IC is the same as the SHUTTLE board.
    3. The bhy2 SDK version is v1.3.0.
    4. The firmware is "Bosch_SHUTTLE_BHI260_AK09915_turbo-flash".
    4. The firmware is "Bosch_SHUTTLE_BHI260_AK09915_turbo.fw".
     
    I want to receive the calibration profile and save it and apply it quickly when it is operated next time.
    So I used bhy2_get_calibration_profile after the accuracy of the virtual sensor I wanted became 3.
    However, -5 (time out) was returned.
    Unregistered virtual sensors are returned 0.
    and Calibration data was also received normally.
     
    I want to know the details of how I can get the data and use it.
     
    If you have a datasheet or detailed document related to bhy2, I'd like to receive it.
    7 REPLIES 7

    BSTRobin
    Community Moderator
    Community Moderator

    Hi hjoungjoo,

    I uploaded attached example code run on STM32 for your reference.
    With BHY2-Sensor-API-1.4.1: https://github.com/boschsensortec/BHY2-Sensor-API

    I checked the example you gave me.
    I tested it in the same way.
    However, the result was the same -5 (timeout).

    BSTRobin
    Community Moderator
    Community Moderator

    Hi hjoungjoo,

    Did you use BHY2-Sensor-API-1.4.1 with example code?
    In addition to obtaining calibration status return timeout error, are other functions (Euler angle example) normal?

    Hi. BSTRobin

    I am using BHY2-Sensor-API-1.3.0 because I use BHI260AB.

    I tested it with 1.4.0, but it was the same.

    I misrepresented the firmware information when I inquired above.
    The firmware you are using is "Bosch_SHUTTLE_BHI260_AK09915_turbo.fw".
    I don't have FLASH, so I'm using it for RAM.

    The sensor values are normal.
    some functions (Ex bhy2_get_orientation_matrix) have the same timeout.

     

    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