About turboscrew

Hmm, I don't use any OS, and the driver in https://github.com/BoschSensortec/BME280_driver seems to use Linux kernel definitions, like U8_C(x) (defined in linux/include/asm-generic/int-ll64.h).       ... View more

Also, I'm not sure how my superiors would like a BSD-3 licenced code in our product.   ... View more

A-ha, digH[4] was formed the wrong way. Reg 0xE4 contains the high part, not the low part. In the case of digH[4], the "endianness" is different from others. But now I'm getting 100%. I think I should be getting about 70%. The raw value divided by 0xFFFF and multiplied by 100% goesn't go even close. The compensation is obviously quite complex.       ... View more

Well, temperature measurement seems to work, and so does pressure measurement. My guess is, that the humidity should be around 30%. (0x5295 / 0xFFFF * 100% = 32.26%) And I already listed the compensation parameters for humidity: "The compensation constants read from the chip are: digH[0] int32_t 75 digH[1] int32_t 397 digH[2] int32_t 0 digH[3] int32_t 783 digH[4] int32_t 50 digH[5] int32_t 30"     ... View more

Instead of polling of chip ID I do: while ((tmp & 0x1) != 0) { /* wait until NVM reading is finished */ tmp = read_reg(BME280_ADDR, BME280_STATUS); } Does this: BME280_MODE_NORMAL & 0x00 mean the chip is to put to sleep? And there is a non-zero value in humidity register(s), but it's such that the compensation algorithm returns zero. buff[6] uint8_t 0x52 (Hex) buff[7] uint8_t 0x95 (Hex) How many bit ADC is used for humidity? The value (0x5295) has 15 bits. It seems like the result is zeroed at: var5 = (var5 < 0 ? 0 : var5); (humidity compensation code from your repo)   ... View more