• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 51 subscribers
  • Views 270 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

CC2650STK: CC2650STK Accelerometer range issues

Josel Go
Expert 6325 points
Part Number: CC2650STK


Hi Experts,

Good day.

Our customer is currently working on an app for my SensorTag cc2650STK and they have some Accelerometer range issues.
currently, the customer is writing 0x0238,0x00 on the Movement Config ID to enable the accelerometer data But the problem is they don't know how to set the Accelerometer range.



This needs to be explained on the docs

Keep safe.

Regards,

Josel

  • +1
    TI__Guru**** 218737 points

    Hi Josel,

    Inside sensor_mpu6500.c the sensorMpu6500Init function calls sensorMpu6500AccSetRange with a value of ACC_RANGE_8G, so that accRangeReg is set to ACC_REG_CTRL_8G for when sensorWriteReg is used inside sensorMpu6500WakeUp.  They can change ACC_RANGE_8G to another valid definition if desired.

    Regards,
    Ryan

  • 0 in reply to Ryan Brown1
    TI__Expert 6325 points

    Hi Ryan,

    The customer is developing an app on android and in order to get data from the Movement Data UUID (0xAA81) you have to write a hex value to Movement Config UUID (0xAA82) now they only using the accelerometer from the Sensortag and in order to activate it, they have to write a hex value to Movement Config ID (0xAA82).
    Currently, they using the hex value 0x0238,0x00 which only activates the Accelerometer bits from the Movement Data UUID as they only need the Accelerometer data. 
    The problem is that they need to write a specific hex value to the (0xAA82) Movement Config UUID in order to set the accelerometer range and WOM features as mentioned in the CC2650STK user guide.  (See the attached image).


    Kindly provide those specific hex values so that they can activate those features just like you have provided the hex values to power off the unit.

    Keep safe.


    Regards,

    Josel

  • 0 in reply to Josel Go
    TI__Guru**** 218737 points

    0x0238 corresponds to 001000111000b which sets bits 3,4,5, and 9.  This corresponds to accelerometer z/y/x axis enabled and accelerometer range 8G.  If they wanted to increase the accelerometer range to 16G then they would also set bit 8, and to enable the WOM they would enable bit 7.  This would be represented as 001110111000b or 0x03B8.

    Regards,
    Ryan