New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CC2650: Wrong scale for accelerometer values #62
Comments
I think we need to set the sensitivity of the accelerometer. Change to 8G or 16GB. |
Indeed, but it is currently not possible with node-sensortag. Should be a parameter of the sensorTag.enableAccelerometer method ? |
@AlexDmr @snowbreeze is the source code to the Android app open source? Do you have a link to it? Which firmware version do you have on the SensorTag? This would probably help resolve #59 as well. Note: bit's 8-9 are used to set the accelerometer range (http://processors.wiki.ti.com/index.php/CC2650_SensorTag_User's_Guide#Configuration_2) node-sensortag is setting config to 0x7f: https://github.com/sandeepmistry/node-sensortag/blob/master/lib/cc2650.js#L108 - does this mean 16G is set? |
Hi, the Android application can be downloaded from the market (sensortag Texas instrument). However i don't think that the code is open source. |
@AlexDmr I'm running firmware version I managed to find some TI code for Android here:
It uses a mask of I've pushed some changes to master, would you mind trying them out? |
Pretty good shot :) |
@AlexDmr excellent, thanks for trying out the changes! I'll publish an updated version to npm shortly. |
Hey.. I've been playing with the CC6250 on Windows. Firmware is 1.20. I currently find it impossible to change accelerometer range. I can easily switch on and off the various gyro, accelerometer, magnetometer and WOM setting and all works as expected but bits 8:9 seem permanently set to 0x02 == 8G (Verified by directly reading the characteristic). Doesn't matter what I do to try and change it, range is stuck at 8G. Seems like a bug in either the firmware or the Windows API i'm using. Not a deal breaker for me but I did waste some time figuring this out. |
@tobybrad Can you tell me what are you writing in place of 0x007 to turn on individual settings. |
I think it's a firmware issue on the SensorTag. |
Hi, thanks for this great project!
I get wrong acelerometer values from my CC2650 sensorTag, I have to multiply values by 4 to get actual acceleration. It seems that the initialisation of scale is not correct?
When I observe values with the Android application values are correct.
Any idea where it could come from ?
The text was updated successfully, but these errors were encountered: