Bosch Sensortec Community

    Showing results for 
    Search instead for 
    Did you mean: 

    BNO055_Read Accelerometer,Magnetometer,Gyroscope data on UART

    BNO055_Read Accelerometer,Magnetometer,Gyroscope data on UART



    I am using BNO055 for reading the yaw,pitch and roll values. How do i read this orientation using UART protocol. I went through the datasheet,seems like we need to send a register read command mentioning the register address and length of data. I am trying the same but not able to read data. Do i need to set the protocol selection to UART first? Is there any precondition to be followed for reading values from register. Am i missing something here.

    Is there any API or LabVIEW drivers available?

    Please guide me through, any quick help would be highly appreciated.

    14 REPLIES 14

    Community Moderator
    Community Moderator

    I think you make some misunderstanding here. 

    Since you are using our BNO USB stick board, this means there is one MCU between host and BNO055.  


    Unless you broken the board connection and using flying wire to connect BNO pin directly to host.

    And the MCU on this board is talking to BNO055 via I2C interface only. 

    The page 1 is the register map of BNO055.   So you can communicate with BNO055 to write its register to set to page 0 or page 1.

    Just use burst read function provided in dll,  you can get all sensor data desired.  then you can parse them afterwards.

    Thanks Vincent. Now able to do burst read to read the Euler angles,Calibration data and parse them later.

    I am callling a function and checking for error code afterwards for each function called.

    I am facing an issue with error handling when the USB stick is removed/unplugged. I observe that the whole application crashes, the desktop development also reacts kind of same.A pop up is thrown to user asking to restart the application manually and when Ok is pressed,application closes down.

    I wanted to know how this is being handled in the API function level, Since i am integrating this sensor as part of an overall monitoring system i cant let the application close when this USB stick is unplugged.Is there any interuppt being called by the MCU FW? 

    Please guide me on how to tackle this situation and handle this error in such a way that the application can pop an error and wait till the USB is plugged again may be for timeout period specified.

    Community Moderator
    Community Moderator

    Development Desktop SW is an evaluation SW for our sensor,  it is not intend to be used to integrated into any customer product. 

    In our HW and SW setup,  the USB stick is power on via USB,  if you unplug the the sensor,  the board have no power any more,  the development desktop will also close all window related to that sensor.  Until next time sensor is plug in,  the SW will go through all initialize steps and send initialize command to sensor. 

    There is no such interrupt you expected in current system structure.

    I'm sorry for that.

    I am sorry I did not elaborate properly. What i meant by application is our LABVIEW application which communicates to the USB stick via the generic API's available. I am not integrating the DD2.0 in my monitoring environment,its just used as a reference for evaluation purpose.

    I wanted to know how the Development Desktop 2.0 software know when the USB is unplugged.Is the FW in the MCU monitoring the power line of USB continuously?

    And is there any way i can know this via any functions available in Generic API's , and is there any way of configuring the system from my LABVIEW application such that it does not kill my application using the Generic API's or by any other method?

    I want to handle my LABVIEW application in a way may be a error display in the UI without killing the application, i am not sure how my application gets killed. Is the MCU FW handling this ? 

    Community Moderator
    Community Moderator

    According to the feedback from our engineer team:

    The disconnected information is NOT provided to the user in current API setup.