Bosch Shared
- Top Results
See all results
- About Spanky
- About Spanky
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
About Spanky
since
05-14-2019
06-05-2019
Spanky
New Poster
5
Posts
0
Likes
0
Solutions
06-05-2019
05:42 AM
It appears that this is a factor of the ODR and OSR. 3.4.1 in the data sheet mentions this, and is sort of what I thought would be the culprit. Oversampling controls the resolution and the low order bits are set to zero unless OSR is 32x. Having all 8 bits zeroed threw me off. Incidentally, the example code on github turns off oversampling. It would be helpful to add some examples of higher resolution settings. I still dont have a good feel for the optimal setting (i.e. what setting yeilds the fastest sample rate as well as highest resolution?) The API kicks out invalid combinations, but I'm still a bit lost for the proper settings. Do you have some cookie-cutter setting combinations?
... View more
06-04-2019
09:35 PM
I went back through and implemented the API from github. Same end results: Just recapping, I expect to read 3 bytes of raw pressure data. The low byte is always zero. Here's the debug output from my read function, which is called by way of the API through bmp3_get_sensor_data(). This is a burst read from addr 0x04 E (210089) SENSOR_TASK: addr=0x84 index=0 val = 0x00 (len=7) <<<< this is the dummy byte at 0x04 E (210089) SENSOR_TASK: addr=0x84 index=1 val = 0x00 (len=7) <<<< this should be the first data byte at 0x04 (which is always zero) E (210089) SENSOR_TASK: addr=0x84 index=2 val = 0xA7 (len=7) <<<< middle pressure byte E (210099) SENSOR_TASK: addr=0x84 index=3 val = 0x6D (len=7) <<<< upper pressure byte E (210099) SENSOR_TASK: addr=0x84 index=4 val = 0x00 (len=7) <<<< this should be the first temperature byte at 0x07 (which is always zero... just like the first pressure byte) E (210109) SENSOR_TASK: addr=0x84 index=5 val = 0xC8 (len=7) <<<< middle temperature byte E (210119) SENSOR_TASK: addr=0x84 index=6 val = 0x84 (len=7) <<<< upper temperature byte
... View more
06-03-2019
11:53 PM
I'm not using it directly, but I am refering to it for writing my code. My best guess at this point is some configuration register is controling those low-order bytes on the raw pressure and temperature data. I was hoping this condition would be something obvious. I am setting the POWER_CTRL register to 0x33, which should set it to normal mode and turn on the temperature and pressure readings. (Incidentally, there is a bit of a type-o or section missing at 4.3.15 in the data sheet). I am leaving all the other parameters defaulted after the powerup, which I believe should be sufficient to populate the 3 pressure and 3 temperature data registers. At startup, I am also reading the calibration data, but I am not currently doing the final conversion. I am just looking at the raw data bytes for now. On the pressure data, when I treat the 3 raw bytes as an int (again, not converted, just raw data), I can tell it is reading some sort of pressure. I can see the reading change according to a relatively significnt elevation change (~10ft), but I am only getting the top 16 bits (of the 24) because the low byte is always reading 0x00 I am reading in a loop following that initial setting of the POWER_CTRL register. I've also doublechecked by way of a read on that POWERCTRL reg as well as checking the DRDY bits in the STATUS register before reading the press/temp data registers.
... View more
06-03-2019
01:57 AM
I am trying to implement the BMP388 (for what its worth, I've done a bunch with the BMP280, so I sort of know my way around). The problem is, when I read the block from address 0x04 (the start of the data registers), the first byte in the pressure and the first byte in the temperature are always zero. The whole dummybyte in the SPI got me for a while, but that is not the issue here (i've tried starting at address 0x03, and read through to 0x09 to verify) I've also read the 3 bytes in sensortime (addr 0x0C) and am seeing the bytes incriment as expected. I'm using the same code for reading the pressure bytes, so I'm at a loss for why the first byte is good in the sensortime, but always zero for the pressure or temperature blocks. For clarification, here is what I am seeing: Addr[0x04] = 0x00 <=== shouldn't this be non-zero, or change over subsequent reads? Addr[0x05] = 0xF2 this fluctuates, which is expected Addr[0x06] = 0x6C this is mostly static, but since it is the high bits, I would expect this behavior as well Addr[0x07] = 0x00 <=== shouldn't this be non-zero Addr[0x08] = 0xBC Addr[0x09] = 0x81 I've tried reading these registers a number of different ways: Single-byte reads for each of the above registers Block read for 0x04-0x06 (and another block read from 0x07-0x09 Block read starting at 0x03 Block read starting at 0x04 From everything I can see, it appears that the first byte for temperature and pressure is just not being set. Any idea what is going on here?
... View more
- Tags:
- BMP388
05-14-2019
04:37 AM
I am having the same problem. I can read the accelerometer and gyro without issue, but the magnetometer is outputting zeroes to the data registers.
... View more
Latest Tags
No tags yet
Still looking for something?
- Top Results
See all results