A few posts ago, I presented the light sensor TSL2561<\/a>, which at first glance works similarly to the BH1750FVI, but has a clear difference in detail. A comparison of this and all other sensors in this series is available when I have completed the series. <\/p>\r\n In this article, I will first discuss the technical features, present the setting options, explain the control via Arduino and present my library for this module. There are already a number of libraries for the BH1750FVI, but I haven’t found one where the setting of the measurement time was implemented or worked according to my expectations. <\/p>\r\n 1<\/sup> A summary of the series can be found here<\/a>.<\/em><\/p>\r\n\n The BH1750FVI has a photodiode with a response range of approx. 400 – 700 nm, i.e. essentially the area of visible light. The photo voltage is amplified and stored with an A\/D converter in a 16-bit reading. The measured value are integrated over an adjustable measurement period. <\/p>\r\n\n The most important technical data are:<\/p>\r\n The standard I2C address of the module is 0x23. You can change it to 0x5C by connecting the address pin (ADDR or ADD) to HIGH. The pin is apparently “pulled down”. Therefore, no connection to GND is necessary for the use of the default address. You can check the address with an I2C scanner, for example the one here<\/a>. <\/p>\r\n\n You can buy the module for about 2 euros, e.g. at Amazon<\/a> from numerous providers. <\/p>\r\n You can get a detailed data sheet here<\/a>.<\/p>\r\n\n The BH1750HVI has three continuous and three discontinuous (“One Time”) modes:<\/p>\r\n The advantage of the “One Time” modes is that the module automatically goes into Power Off mode after the measurement and thus saves power. <\/p>\r\n Otherwise, the modes differ in terms of resolution and measurement time: <\/p>\r\n\n The continuous H-Resolution Mode is the default. You go into L-Resolution Mode if you want to measure fast or at high frequency. The H-Resolution Mode2 is a good way to achieve a higher resolution in the dark. <\/p>\r\n\n The measured value is stored as a 16 bit value, correspondingly 65535 is the maximum value. To convert the measured values into Lux, the raw data in H-Resolution and L-Resolution Mode must be divided by 1.2, according to the data sheet. This results in a maximum value of 54612 lx. In H-Resolution Mode2, the result must be divided by two again. This results in a maximum value of 27306 lx.\u00a0<\/p>\n\n If you are not using a library, you only need to send a single control byte (called OpeCode in the data sheet) to the BH1750HVI via I2C to set the desired mode. Later you can see in the example sketches how this works in detail. <\/p>\r\n\n Frankly, I had to read the section on the setting procedure of the measurement time several times because it is, let’s say, unusual. First, one should know that the setting of the measuring time is relative to the basic measurement time set by the mode, i.e. 16 or 120 ms. This means that you do not specify a value in milliseconds, but work with factors.\u00a0<\/p>\r\n The measurement time or factor is set in the Measurement Time Register (MTReg). \u00a0 The default setting is 69 (0b01000101). This value can be varied from 31 to 254. A change to 31 means:<\/p>\r\n A change to the maximum value 254 means:<\/p>\r\n The measuring time can be changed by a factor of 0.45 to 3.68.\u00a0<\/p>\r\n The measurement time change is directly proportional to the raw data. Accordingly, the maximum measurable light intensity changes. For example, in Continuous H mode, the maximum measurable Lux value is 65535 \/ 1.2 \u2248 54612. If the measuring time is reduced to the 0.45fold, the light can be correspondingly more intense without the 16-bit data register overflowing. The maximum measurable value in Lux is thus 65535 x (69\/31) \/ 1.2 \u2248 121557 lx. I don’t know why the data sheet specifies 100000 lx as the maximum value.<\/p>\r\n It is important to take the factors into account when converting the raw data into lux values, otherwise the results are wrong. However, there may also be a reason not to do this, and that is when you are performing a calibration. More on that. \u00a0 \u00a0\u00a0<\/p>\n\n There are three reasons to change the measurement time:<\/p>\r\n Let’s say the BH1750FVI is installed behind a window that only passes through 50% of the light. In this case, the measuring time would be doubled to compensate for the effect (calibration). And in this case, of course, the factor would not be factored out at the end, as in 1 and 2.\u00a0<\/p>\n\n Derived from the calculation rules given above, the resolution can be determined depending on the MTReg value:<\/p>\r\n This results in:<\/p>\n\n In principle, I have already given the answer. You need to change the default value in MTReg from 69 to the desired value. If you have a library that has implemented this feature, you don’t have to worry about the details and can skip the rest of the section. <\/p>\r\n For those who work without a library or want to change something in their library or just want to know what’s going on behind the scenes, I’ll explain that. <\/p>\r\n You are normally used to changing a register value by addressing a control register, passing the destination register address, and then sending the values \u200b\u200bbyte by byte. Things are a little different here. The three upper bits and the five lower bits of the MTReg value (short: MTReg) are passed to the BH1750FVI in two steps, packaged in two control bytes. This happens according to the following scheme:<\/p>\r\n The best way to calculate the bytes is by binary operations:<\/p>\r\n The 5 digit shift positions the bits 7,6 and 5 in the correct position. The subsequent logical OR operation ensures that the lower bits remain unchanged and the higher bits are 01000.<\/p>\r\n Here, the first logical AND ensures write a 0 in bit 7 of the byte2 without changing the other bits. The subsequent OR operation sets bits 6 and 7 without changing the other bits. <\/p>\r\n\n Here are a few more settings with the corresponding OpeCodes:<\/p>\r\n\n Here is the Arduino Sketch for controlling the BH1750FVI without a library.<\/p>\r\n The MTReg value (measuringTimeFactor) is entered as a factor and the byte value for the MT register is calculated from it. I find this more practical than setting the MTReg value directly. In line 38 and 41, the factor is factored out again to get the “real” Lux values. If the factor is used for calibration, this calculation step must be omitted. <\/p>\r\n Based on the previous explanations, the sketch should be self-explanatory. <\/p>\r\n\n <\/p>\r\n<\/div>\n\n For completeness, here is the circuit, even if it is anything but complex. It should be noted that I did not use pull-up resistors for the SDA \/ SCL lines. It also works without. If you get problems, add them. <\/p>\r\n\n Since, as already mentioned, I did not find a library where the setting of the measurement time was implemented to my satisfaction, I wrote my own. It’s called BH1750_WE and you’ll find it here<\/a> on Github. If you want to work with it, download it as a zip file and unpack it in the Arduino\/libraries folder. The following example sketch can be found in the example folder. (New: you can now also install the library directly via the library manager in the Arduino IDE<\/em>). <\/p>\r\n\n \u00a0<\/p>\r\n<\/div>\n\n For measurements in one time modes, please note that \u00a0<\/p>\r\n<\/div>\r\n\n The background for the post image is by Hanna Kovalchuk<\/a> on Pixabay<\/a>.<\/p>\r\nProperties<\/h2>\n\n
![\"Various](\"https:\/\/wolles-elektronikkiste.de\/wp-content\/uploads\/2019\/09\/BH1750_beide_Modelle-1024x414.jpg\")
<\/a>Principle<\/h3>\n\n
Specifications of the BH1750FVI module<\/h3>\n\n
\r\n
\r\n
\r\n
Setting options \/ operating modes<\/h2>\n\n
Resolution modes<\/h3>\n\n
\r\n
![\"\"](\"https:\/\/wolles-elektronikkiste.de\/wp-content\/uploads\/2019\/09\/Modes_vs_res_vs_mt.png\")
<\/a>Resolution vs maximum light intensity<\/h4>\n\n
How to set the modes<\/h4>\n\n
![\"OpeCodes](\"https:\/\/wolles-elektronikkiste.de\/wp-content\/uploads\/2020\/11\/Mode_vs_OpCode.png\")
<\/a>Setting the measurement time<\/h3>\n\n
New measurement time = base value x 31\/69 \u2248 base value x 0,45<\/code><\/p>\r\nNew measurement time = base value x 254\/69 \u2248 base value x 3,68<\/code><\/p>\r\nWhy change the measurement time? <\/h4>\n\n
\r\n\t
Resolution versus measurement time<\/h4>\n\n
Resolution in H-Resolution Mode = 1\/1.2 x 69\/MTReg<\/code><\/p>\r\nResolution in H-Resolution Mode2 = (1\/1.2 x 69\/MTReg)\/2\u00a0<\/code><\/p>\r\nResolution in L-Resolution Mode = (1\/1.2 x 69\/MTReg) x 4<\/code><\/p>\r\n![\"Resolution](\"https:\/\/wolles-elektronikkiste.de\/wp-content\/uploads\/2020\/11\/Resolution_vs_MTReg-1024x192.png\")
<\/a>How to change the measurement time<\/h4>\n\n
\r\n
Byte1 = (MTReg >> 5) | 0b01000000<\/code><\/p>\r\nByte2 = (MTReg & 0b01111111) | 0b01100000<\/code><\/p>\r\nOther settings<\/h3>\n\n
![\"More](\"https:\/\/wolles-elektronikkiste.de\/wp-content\/uploads\/2020\/11\/Other_Settings.png\")
<\/a><\/figure>\n\nControl of the BH1750FVI without library <\/h2>\n\n
The sketch<\/h3>\n\n
#include\u00a0<Wire.h>\r\n#define\u00a0BH_1750\u00a00x23\r\n#define\u00a0DATA_REG_RESET\u00a00b00000111\r\n#define\u00a0POWER_DOWN\u00a00b00000000\r\n#define\u00a0POWER_ON\u00a00b00000001\r\n\r\nenum\u00a0BH1750Mode\u00a0{\r\n\u00a0\u00a0CHM\u00a0=\u00a00b00010000,\u00a0\u00a0\u00a0\u00a0\u00a0\/\/CHM:\u00a0Continuously\u00a0H-Resolution\u00a0Mode\r\n\u00a0\u00a0CHM_2\u00a0=\u00a00b00010001,\u00a0\u00a0\u00a0\/\/CHM_2:\u00a0Continuously\u00a0H-Resolution\u00a0Mode2\r\n\u00a0\u00a0CLM\u00a0=\u00a00b00010011,\u00a0\u00a0\u00a0\u00a0\u00a0\/\/CLM:\u00a0Continuously\u00a0L-Resolution\u00a0Mode\r\n\u00a0\u00a0OTH\u00a0=\u00a00b00100000,\u00a0\u00a0\u00a0\u00a0\u00a0\/\/OTH:\u00a0One\u00a0Time\u00a0H-Resolution\u00a0Mode\r\n\u00a0\u00a0OTH_2\u00a0=\u00a00b00100001,\u00a0\u00a0\u00a0\/\/OTH_2:\u00a0One\u00a0Time\u00a0H-Resolution\u00a0Mode2\r\n\u00a0\u00a0OTL\u00a0=\u00a00b00100011\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\/\/OTL:\u00a0One\u00a0Time\u00a0L-Resolution\u00a0Mode\r\n}\u00a0mode;\r\n\r\nfloat\u00a0measuringTimeFactor;\r\n\r\nvoid\u00a0setup(){\r\n\u00a0\u00a0Serial.begin(9600);\r\n\u00a0\u00a0Wire.begin();\r\n\u00a0\u00a0mode\u00a0=\u00a0CHM;\r\n\u00a0\u00a0measuringTimeFactor\u00a0=\u00a01;\r\n\u00a0\u00a0setMode();\r\n\u00a0\u00a0setMeasuringTime();\u00a0\r\n\u00a0\u00a0delay(200);\r\n}\r\n\r\nvoid\u00a0loop(){\u00a0\r\n\u00a0\u00a0getLux();\r\n\u00a0\u00a0delay(1000);\r\n}\r\n\r\nvoid\u00a0getLux(){\r\n\u00a0\u00a0uint16_t\u00a0rawLux;\r\n\u00a0\u00a0float\u00a0lux;\r\n\u00a0\u00a0rawLux\u00a0=\u00a0readBH1750();\r\n\u00a0\u00a0if((mode==CHM_2)||(mode==OTH_2)){\r\n\u00a0\u00a0\u00a0\u00a0lux\u00a0=\u00a0(rawLux\/2.4)\/measuringTimeFactor;\u00a0\u00a0\u00a0\u00a0\u00a0\r\n\u00a0\u00a0}\r\n\u00a0\u00a0else{\r\n\u00a0\u00a0\u00a0\u00a0lux\u00a0=\u00a0(rawLux\/1.2)\/measuringTimeFactor;\r\n\u00a0\u00a0}\r\n\u00a0\u00a0Serial.print(F(\"Lichtst\u00e4rke:\u00a0\"));\r\n\u00a0\u00a0Serial.print(lux);\r\n\u00a0\u00a0Serial.println(F(\"\u00a0Lux\"));\r\n}\r\n\r\nvoid\u00a0powerDown(){\r\n\u00a0\u00a0writeBH1750(POWER_DOWN);\r\n}\r\n\r\nvoid\u00a0powerOn(){\r\n\u00a0\u00a0writeBH1750(POWER_ON);\r\n\u00a0\u00a0setMode();\r\n}\r\n\r\nvoid\u00a0dataRegReset(){\r\n\u00a0\u00a0writeBH1750(DATA_REG_RESET);\r\n}\r\n\r\nvoid\u00a0setMode(){\r\n\u00a0\u00a0writeBH1750(mode);\r\n}\r\n\r\nvoid\u00a0setMeasuringTime(){\r\n\u00a0\u00a0byte\u00a0mt\u00a0=\u00a0round(measuringTimeFactor*69);\r\n\u00a0\u00a0byte\u00a0highByteMT\u00a0=\u00a0((mt>>5)\u00a0|\u00a00b01000000);\r\n\u00a0\u00a0byte\u00a0lowByteMT\u00a0=\u00a0(mt\u00a0&\u00a00b01111111);\r\n\u00a0\u00a0lowByteMT\u00a0|=\u00a00b01100000;\r\n\u00a0\u00a0writeBH1750(highByteMT);\r\n\u00a0\u00a0writeBH1750(lowByteMT);\r\n}\r\n\r\nuint16_t\u00a0readBH1750(){\r\n\u00a0\u00a0uint8_t\u00a0MSbyte,\u00a0LSbyte;\r\n\u00a0\u00a0Wire.requestFrom(BH_1750,\u00a02);\r\n\u00a0\u00a0if(Wire.available()){\r\n\u00a0\u00a0\u00a0\u00a0MSbyte=Wire.read();\r\n\u00a0\u00a0\u00a0\u00a0LSbyte=Wire.read();\u00a0\r\n\u00a0\u00a0}\r\n\u00a0\u00a0return\u00a0((MSbyte<<8)\u00a0+\u00a0LSbyte);\r\n}\r\n\r\nvoid\u00a0writeBH1750(byte\u00a0val){\r\n\u00a0\u00a0Wire.beginTransmission(BH_1750);\r\n\u00a0\u00a0Wire.write(val);\r\n\u00a0\u00a0Wire.endTransmission();\r\n}<\/pre>\r\nWiring <\/h3>\n\n
![\"Circuit:](\"https:\/\/wolles-elektronikkiste.de\/wp-content\/uploads\/2019\/09\/BH1750FVI_Wiring.png\")
<\/a>BH1750FVI Library<\/h2>\n\n
\/***************************************************************************\r\n* Example sketch for the BH1750_WE library\r\n* \r\n* Mode selection \/ abbreviations:\r\n* CHM: Continuously H-Resolution Mode\r\n* CHM_2: Continuously H-Resolution Mode2\r\n* CLM: Continuously L-Resolution Mode\r\n* OTH: One Time H-Resolution Mode\r\n* OTH_2: One Time H-Resolution Mode2\r\n* OTL: One Time L-Resolution Mode\r\n* \r\n* Measuring time factor:\r\n* 1.0 ==> Mresuring Time Register = 69\r\n* 0.45 ==> Measuring Time Register = 31\r\n* 3.68 ==> Mesuring Time Register = 254\r\n* \r\n* Other implemented functions, not used in the example:\r\n* resetDataReg() --> rests Data Register\r\n* powerOn() --> Wake Up!\r\n* powerDown() --> Sleep well, my BH1750\r\n* \r\n* If you change the measuring time factor for calibration purpose, \r\n* then you need to devide the light intensity by the measuring time factor \r\n* \r\n* Further information can be found on:\r\n* https:\/\/wolles-elektronikkiste.de\/en\/bh1750fvi-gy-30-302-ambient-light-sensor\r\n* or in German:\r\n* https:\/\/wolles-elektronikkiste.de\/bh1750fvi-lichtsensormodul\r\n***************************************************************************\/\r\n\r\n#include <Wire.h>\r\n#include <BH1750_WE.h>\r\n#define BH1750_ADDRESS 0x23\r\n\r\nBH1750_WE myBH1750(BH1750_ADDRESS); \r\n\/\/ You may also pass a TwoWire object like wire2 \r\n\/\/ BH1750_WE myBH1750(&wire2, BH1750_ADDRESS);\r\n\r\nvoid setup(){\r\n Serial.begin(9600);\r\n Wire.begin();\r\n myBH1750.init(); \/\/ sets default values: mode = CHM, measuring time factor = 1.0\r\n \/\/ myBH1750.setMode(CLM); \/\/ uncomment if you want to change default values\r\n \/\/ myBH1750.setMeasuringTimeFactor(0.45); \/\/ uncomment for selection of value between 0.45 and 3.68\r\n}\r\n\r\nvoid loop(){ \r\n float lightIntensity = myBH1750.getLux();\r\n Serial.print(F(\"Lichtst\u00e4rke: \"));\r\n Serial.print(lightIntensity);\r\n Serial.println(F(\" Lux\"));\r\n delay(1000);\r\n}<\/pre>\r\nMeasurements in One Time Modes<\/h3>\n\n
setMode()<\/code> starts the measurement. You have to wait until the measurement is complete, and then you can read out the new measured value. According to the data sheet, a measurement in OTH modes takes approx. 120 milliseconds, in OTL mode it takes 16 milliseconds.<\/p>\r\n\n#include <Wire.h>\r\n#include <BH1750_WE.h>\r\n#define BH1750_ADDRESS 0x23\r\n\r\nBH1750_WE myBH1750 = BH1750_WE(BH1750_ADDRESS); \r\n\/\/ You may also pass a TwoWire object: \r\n\/\/BH1750_WE myBH1750 = BH1750_WE(&Wire, BH1750_ADDRESS);\r\n\/\/ If you don't pass any parameter, Wire and 0x23 will be applied\r\n\r\nvoid setup(){\r\n Serial.begin(9600);\r\n Wire.begin();\r\n if(!myBH1750.init()){ \/\/ sets default values: mode = CHM, measuring time factor = 1.0\r\n Serial.println(\"Connection to the BH1750 failed\");\r\n Serial.println(\"Check wiring and I2C address\");\r\n while(1){}\r\n }\r\n else{\r\n Serial.println(\"BH1750 is connected\");\r\n }\r\n \/\/ myBH1750.setMeasuringTimeFactor(0.45); \/\/ uncomment for selection of value between 0.45 and 3.68\r\n}\r\n\r\nvoid loop(){ \r\n myBH1750.setMode(OTH); \/\/ sets mode and starts measurement\r\n \/* An OTH and OTH_2 measurement takes ~120 ms. I suggest to wait \r\n 140 ms to be on the safe side. \r\n An OTL measurement takes about 16 ms. I suggest to wait 20 ms\r\n to be on the safe side. *\/\r\n delay(140); \/\/ wait for measurement to be completed.\r\n float lightIntensity = myBH1750.getLux();\r\n Serial.print(F(\"Light intensity: \"));\r\n Serial.print(lightIntensity);\r\n Serial.println(F(\" Lux\"));\r\n delay(1000);\r\n}<\/pre>\r\nAcknowledgement<\/h2>\n\n