ZHCSF44A May 2016 – June 2016 OPT3002
PRODUCTION DATA.
- 1 特性
- 2 應(yīng)用
- 3 說明
- 4 修訂歷史記錄
- 5 Pin Configuration and Functions
- 6 Specifications
- 7 Detailed Description
- 8 Application and Implementation
- 9 Power-Supply Recommendations
- 10Layout
- 11器件和文檔支持
- 12機(jī)械、封裝和可訂購信息
封裝選項(xiàng)
機(jī)械數(shù)據(jù) (封裝 | 引腳)
- DNP|6
散熱焊盤機(jī)械數(shù)據(jù) (封裝 | 引腳)
訂購信息
7 Detailed Description
7.1 Overview
The OPT3002 measures the light that illuminates the device within the device spectral range of 300 nm to 1000 nm.
The OPT3002 is fully self-contained to measure the ambient light and report the result digitally over the I2C bus. The result can also be used to alert a system and interrupt a processor with the INT pin. The result can also be summarized with a programmable window comparison and communicated with the INT pin.
The OPT3002 can be configured into an automatic full-scale, range-setting mode that always selects the optimal full-scale range setting for the lighting conditions. This mode automatically selects the optimal full-scale range for the given lighting condition, thus eliminating the requirement of programming many measurement and readjustment cycles of the full-scale range. The device can operate continuously or in single-shot measurement modes.
The device integrates its result over either 100 ms or 800 ms, so the effects of 50-Hz and 60-Hz noise sources from typical light bulbs are nominally reduced to a minimum.
The device starts up in a low-power shutdown state, such that the OPT3002 only consumes active-operation power after being programmed into an active state.
7.2 Functional Block Diagram
7.3 Feature Description
7.3.1 Automatic Full-Scale Range Setting
The OPT3002 has an automatic full-scale range setting feature that eliminates the need to predict and set the optimal range for the device. In this mode, the OPT3002 automatically selects the optimal full-scale range for the given lighting condition. The OPT3002 has a high degree of result matching between the full-scale range settings. This matching eliminates the problem of varying results or the need for range-specific, user-calibrated gain factors when different full-scale ranges are chosen. For further details, see the Automatic Full-Scale Setting Mode section.
7.3.2 Interrupt Operation, INT Pin, and Interrupt Reporting Mechanisms
The device has an interrupt reporting system that allows the processor connected to the I2C bus to go to sleep, or otherwise ignore the device results, until a user-defined event occurs that requires possible action. Alternatively, this same mechanism can also be used with any system that can take advantage of a single digital signal that indicates whether the light is above or below the levels of interest.
The interrupt event conditions are controlled by the high-limit and low-limit registers, as well as the configuration register latch and fault count fields. The results of comparing the result register with the high-limit register and low-limit register are referred to as fault events. The fault count field (configuration register, bits FC[1:0]) dictates how many consecutive same-result fault events are required to trigger an interrupt event and subsequently change the state of the interrupt reporting mechanisms (that is, the INT pin, the flag high field, and the flag low field). The latch field allows a choice between a latched window-style comparison and a transparent hysteresis-style comparison.
The INT pin has an open-drain output that requires the use of a pullup resistor. This open-drain output allows multiple devices with open-drain INT pins to be connected to the same line, thus creating a logical NOR or AND function between the devices. The polarity of the INT pin can be controlled with the polarity of the interrupt field in the configuration register. When the POL field is set to 0, the pin operates in an active low behavior that pulls the pin low when the INT pin becomes active. When the POL field is set to 1, the pin operates in an active high behavior and becomes high impedance, thus allowing the pin to go high when the INT pin becomes active.
Additional details of the interrupt reporting registers are described in the Interrupt Reporting Mechanism Modes and Internal Registers sections.
7.3.3 I2C Bus Overview
The OPT3002 offers compatibility with both I2C and SMBus interfaces. The I2C and SMBus protocols are essentially compatible with one another. The I2C interface is used throughout this document as the primary example with the SMBus protocol specified only when a difference between the two protocols is discussed.
The OPT3002 is connected to the bus with two pins: an SCL clock input pin and an SDA open-drain bidirectional data pin. The bus must be controlled by a master device that generates the serial clock (SCL), controls the bus access, and generates start and stop conditions. To address a specific device, the master initiates a start condition by pulling the data signal line (SDA) from a high logic level to a low logic level when SCL is high. All slaves on the bus shift in the slave address byte on the SCL rising edge, with the last bit indicating whether a read or write operation is intended. During the ninth clock pulse, the slave being addressed responds to the master by generating an acknowledge bit by pulling SDA low.
Data transfer is then initiated and eight bits of data are sent, followed by an acknowledge bit. During data transfer, SDA must remain stable when SCL is high. Any change in SDA when SCL is high is interpreted as a start or stop condition. When all data are transferred, the master generates a stop condition, as indicated by pulling SDA from low to high when SCL is high. The OPT3002 includes a 28-ms timeout on the I2C interface to prevent locking up the bus. If the SCL line is held low for this duration of time, then the bus state machine is reset.
7.3.3.1 Serial Bus Address
To communicate with the OPT3002, the master must first initiate an I2C start command. Then, the master must address slave devices via a slave address byte. The slave address byte consists of seven address bits and a direction bit that indicates whether the action is to be a read or write operation.
Four I2C addresses are possible by connecting the ADDR pin to one of four pins: GND, VDD, SDA, or SCL. Table 1 summarizes the possible addresses with the corresponding ADDR pin configuration. The state of the ADDR pin is sampled on every bus communication and must be driven or connected to the desired level before any activity on the interface occurs.
Table 1. Possible I2C Addresses with the Corresponding ADDR Configuration
| DEVICE I2C ADDRESS | ADDR PIN |
|---|---|
| 1000100 | GND |
| 1000101 | VDD |
| 1000110 | SDA |
| 1000111 | SCL |
7.3.3.2 Serial Interface
The OPT3002 operates as a slave device on both the I2C bus and SMBus. Connections to the bus are made via the SCL clock input line and the SDA open-drain I/O line. The OPT3002 supports the transmission protocol for standard mode (up to 100 kHz), fast mode (up to 400 kHz), and high-speed mode (up to 2.6 MHz). All data bytes are transmitted most-significant bits first.
The SDA and SCL pins feature integrated spike-suppression filters and Schmitt triggers to minimize the effects of input spikes and bus noise. See the Electrical Interface section for further details of the I2C bus noise immunity.
7.4 Device Functional Modes
7.4.1 Automatic Full-Scale Setting Mode
The OPT3002 has an automatic full-scale-range setting mode that eliminates the need for a user to predict and set the optimal range for the device. This mode is entered when the configuration register range number field (RN[3:0]) is set to 1100b.
The first measurement that the device takes in auto-range mode is a 10-ms range assessment measurement. The device then determines the appropriate full-scale range to take its first full measurement.
For subsequent measurements, the full-scale range is set by the result of the previous measurement. If a measurement is towards the low side of full-scale, then the full-scale range is decreased by one or two settings for the next measurement. If a measurement is towards the upper side of full-scale, then the full-scale range is increased by one setting for the next measurement.
If the measurement exceeds the full-scale range, resulting from a fast-increasing optical transient event, then the current measurement is aborted. This invalid measurement is not reported. A 10-ms measurement is taken to assess and properly reset the full-scale range. Then, a new measurement is taken with this proper full-scale range. Therefore, during a fast-increasing optical transient in this mode, a measurement can possibly take longer to complete and report than indicated by the configuration register conversion time field (CT).
7.4.2 Interrupt Reporting Mechanism Modes
There are two major types of interrupt reporting mechanism modes: latched window-style comparison mode and transparent hysteresis-style comparison mode. The configuration register latch field (L) (see the configuration register, bit 4) controls which of these two modes is used. An end-of-conversion mode is also associated with each major mode type. The end-of-conversion mode is active when the two most significant bits of the threshold low register are set to 11b. The mechanisms report via the flag high and flag low fields, the conversion ready field, and the INT pin.
7.4.2.1 Latched Window-Style Comparison Mode
The latched window-style comparison mode is typically selected when using the OPT3002 to interrupt an external processor. In this mode, a fault is recognized when the input signal is above the high-limit register or below the low-limit register. When the consecutive fault events trigger the interrupt reporting mechanisms, these mechanisms are latched, thus reporting whether the fault is the result of a high or low comparison. These mechanisms remain latched until the configuration register is read, which clears the INT pin and flag high and flag low fields. The SMBus alert response protocol, described in detail in the SMBus Alert Response section, clears the pin but does not clear the flag high and flag low fields. The behavior of this mode, along with the conversion ready flag, is summarized in Table 2. Note that Table 2 does not apply when the two threshold low register MSBs (see the Transparent Hysteresis-Style Comparison Mode section for clarification on the MSBs) are set to 11b.
Table 2. Latched Window-Style Comparison Mode: Flag Setting and Clearing Summary(2)(4)
| OPERATION | FLAG HIGH FIELD | FLAG LOW FIELD | INT PIN(1) | CONVERSION READY FIELD |
|---|---|---|---|---|
| The result register is above the high-limit register for fault count times; see the result register and the high-limit register for further details. | 1 | X | Active | 1 |
| The result register is below the low-limit register for fault count times; see the result register and the low-limit register for further details. | X | 1 | Active | 1 |
| The conversion is complete with fault count criterion not met | X | X | X | 1 |
| Configuration register read(3) | 0 | 0 | Inactive | 0 |
| Configuration register write, M[1:0] = 00b (shutdown) | X | X | X | X |
| Configuration register write, M[1:0] > 00b (not shutdown) | X | X | X | 0 |
| SMBus alert response protocol | X | X | Inactive | X |
7.4.2.2 Transparent Hysteresis-Style Comparison Mode
The transparent hysteresis-style comparison mode is typically used when a single digital signal is desired that indicates whether the input light is higher than or lower than a light level of interest. If the result register is higher than the high-limit register for a consecutive number of events set by the fault count field, then the INT line is set to active, the flag high field is set to 1, and the flag low field is set to 0. If the result register is lower than the low-limit register for a consecutive number of events set by the fault count field, then the INT line is set to inactive, the flag low field is set to 1, and the flag high field is set to 0. The INT pin and flag high and flag low fields do not change state with configuration reads and writes. The INT pin and flag fields continually report the appropriate comparison of the light to the low-limit and high-limit registers. The device does not respond to the SMBus alert response protocol when in either of the two transparent comparison modes (configuration register, latch field = 0). The behavior of this mode, along with the conversion ready is summarized in Table 3. Note that Table 3 does not apply when the two threshold low register MSBs (LE[3:2] from Table 11) are set to 11.
Table 3. Transparent Hysteresis-Style Comparison Mode: Flag Setting and Clearing Summary(2)(4)
| OPERATION | FLAG HIGH FIELD | FLAG LOW FIELD | INT PIN(1) | CONVERSION READY FIELD |
|---|---|---|---|---|
| The result register is above the high-limit register for fault count times; see the result register and the high-limit register for further details. | 1 | 0 | Active | 1 |
| The result register is below the low-limit register for fault count times; see the result register and the low-limit register for further details. | 0 | 1 | Inactive | 1 |
| The conversion is complete with fault count criterion not met | X | X | X | 1 |
| Configuration register read(3) | X | X | X | 0 |
| Configuration register write, M[1:0] = 00b (shutdown) | X | X | X | X |
| Configuration register write, M[1:0] > 00b (not shutdown) | X | X | X | 0 |
| SMBus alert response protocol | X | X | X | X |
7.4.2.3 End-of-Conversion Mode
An end-of-conversion indicator mode can be used when every measurement is desired to be read by the processor, prompted by the INT pin going active on every measurement completion. This mode is entered by setting the most significant two bits of the low-limit register (LE[3:2] from the low-limit register) to 11b. This end-of-conversion mode is typically used in conjunction with the latched window-style comparison mode. The INT pin becomes inactive when the configuration register is read or the configuration register is written with a non-shutdown parameter or in response to an SMBus alert response. Table 4 summarizes the interrupt reporting mechanisms as a result of various operations.
Table 4. End-of-Conversion Mode When in Latched Window-Style Comparison Mode:
Flag Setting and Clearing Summary(2)
| OPERATION | FLAG HIGH FIELD | FLAG LOW FIELD | INT PIN(1) | CONVERSION READY FIELD |
|---|---|---|---|---|
| The result register is above the high-limit register for fault count times; see the result register and the high-limit register for further details. | 1 | X | Active | 1 |
| The result register is below the low-limit register for fault count times; see the result register and the low-limit register for further details. | X | 1 | Active | 1 |
| The conversion is complete with fault count criterion not met | X | X | Active | 1 |
| Configuration register read(3) | 0 | 0 | Inactive | 0 |
| Configuration register write, M[1:0] = 00b (shutdown) | X | X | X | X |
| Configuration register write, M[1:0] > 00b (not shutdown) | X | X | X | 0 |
| SMBus alert response protocol | X | X | Inactive | X |
Note that when transitioning from end-of-conversion mode to the standard comparison modes (that is, programming LE[3:2] from 11b to 00b) when the configuration register latch field (L) is 1, a subsequent write to the configuration register latch field (L) to 0 is necessary in order to properly clear the INT pin. The latch field can then be set back to 1 if desired.
7.4.2.4 End-of-Conversion and Transparent Hysteresis-Style Comparison Mode
The combination of end-of-conversion mode and transparent hysteresis-style comparison mode can also be programmed simultaneously. The behavior of this combination is shown in Table 5.
Table 5. End-Of-Conversion Mode When in Transparent Hysteresis-Style Comparison Mode:
Flag Setting and Clearing Summary(2)
| OPERATION | FLAG HIGH FIELD | FLAG LOW FIELD | INT PIN(1) | CONVERSION READY FIELD |
|---|---|---|---|---|
| The result register is above the high-limit register for fault count times; see the result register and the high-limit register for further details. | 1 | 0 | Active | 1 |
| The result register is below the low-limit register for fault count times; see the result register and the low-limit register for further details. | 0 | 1 | Active | 1 |
| The conversion is complete with fault count criterion not met | X | X | Active | 1 |
| Configuration register read(3) | X | X | Inactive | 0 |
| Configuration register write, M[1:0] = 00b (shutdown) | X | X | X | X |
| Configuration register write, M[1:0] > 00b (not shutdown) | X | X | Inactive | 0 |
| SMBus alert response protocol | X | X | X | X |
7.5 Programming
The OPT3002 supports the transmission protocol for standard mode (up to 100 kHz), fast mode (up to 400 kHz), and high-speed mode (up to 2.6 MHz). Fast and standard modes are described as the default protocol, referred to as F/S. High-speed mode is described in the High-Speed I2C Mode section.
7.5.1 Writing and Reading
Accessing a specific register on the OPT3002 is accomplished by writing the appropriate register address during the I2C transaction sequence. See Table 6 for a complete list of registers and the corresponding register addresses. The value for the register address (as shown in Figure 15) is the first byte transferred after the slave address byte with the R/W bit low.
NOINDENT:
The value of the slave address byte is determined by the ADDR pin setting; see Table 1.Writing to a register begins with the first byte transmitted by the master. This byte is the slave address with the R/W bit low. The OPT3002 then acknowledges receipt of a valid address. The next byte transmitted by the master is the address of the register that data are to be written to. The next two bytes are written to the register addressed by the register address. The OPT3002 acknowledges receipt of each data byte. The master can terminate the data transfer by generating a start or stop condition.
When reading from the OPT3002, the last value stored in the register address by a write operation determines which register is read during a read operation. To change the register address for a read operation, a new partial I2C write transaction must be initiated. This partial write is accomplished by issuing a slave address byte with the R/W bit low, followed by the register address byte and a stop command. The master then generates a start condition and sends the slave address byte with the R/W bit high to initiate the read command. The next byte is transmitted by the slave and is the most significant byte of the register indicated by the register address. This byte is followed by an acknowledge from the master; then the slave transmits the least significant byte. The master acknowledges receipt of the data byte. The master can terminate the data transfer by generating a not-acknowledge after receiving any data byte, or by generating a start or stop condition. If repeated reads from the same register are desired, continually sending the register address bytes is not necessary; the OPT3002 retains the register address until that number is changed by the next write operation.
Figure 16 and Figure 17 show the write and read operation timing diagrams, respectively. Note that register bytes are sent most significant byte first, followed by the least significant byte.
NOINDENT:
The value of the slave address byte is determined by the setting of the ADDR pin; see Table 1.
NOINDENT:
The value of the slave address byte is determined by the ADDR pin setting; see Table 1.NOINDENT:
An ACK by the master can also be sent.7.5.1.1 High-Speed I2C Mode
When the bus is idle, both the SDA and SCL lines are pulled high by the pullup resistors or the active pullup devices. The master generates a start condition followed by a valid serial byte containing the high-speed (HS) master code 0000 1XXXb. This transmission is made in either standard mode or fast mode (up to 400 kHz). The OPT3002 does not acknowledge the HS master code but does recognize the code and switches its internal filters to support a 2.6-MHz operation.
The master then generates a repeated start condition (a repeated start condition has the same timing as the start condition). After this repeated start condition, the protocol is the same as F/S mode, except that transmission speeds up to 2.6 MHz are allowed. Instead of using a stop condition, use repeated start conditions to secure the bus in HS mode. A stop condition ends the HS mode and switches all internal filters of the OPT3002 to support the F/S mode.
7.5.1.2 General-Call Reset Command
The I2C general-call reset allows the host controller in one command to reset all devices on the bus that respond to the general-call reset command. The general call is initiated by writing to the I2C address 0 (0000 0000b). The reset command is initiated when the subsequent second address byte is 06h (0000 0110b). With this transaction, the device issues an acknowledge bit and sets all of its registers to the power-on-reset default condition.
7.5.1.3 SMBus Alert Response
The SMBus alert response provides a quick identification for which device issued the interrupt. Without this alert response capability, the processor does not know which device pulled the interrupt line when there are multiple slave devices connected.
The OPT3002 is designed to respond to the SMBus alert response address, when in the latched window-style comparison mode (configuration register, latch field = 1). The OPT3002 does not respond to the SMBus alert response when in transparent mode (configuration register, latch field = 0).
The response behavior of the OPT3002 to the SMBus alert response is shown in Figure 18. When the interrupt line to the processor is pulled to active, the master can broadcast the alert response slave address (0001 1001b). Following this alert response, any slave devices that generated an alert identify themselves by acknowledging the alert response and sending their respective I2C address on the bus. The alert response can activate several different slave devices simultaneously. If more than one slave attempts to respond, bus arbitration rules apply. The device with the lowest address wins the arbitration. If the OPT3002 loses the arbitration, then the device does not acknowledge the I2C transaction and its INT pin remains in an active state, prompting the I2C master processor to issue a subsequent SMBus alert response. When the OPT3002 wins the arbitration, the device acknowledges the transaction and sets its INT pin to inactive. The master can issue that same command again, as many times as necessary to clear the INT pin. See the Interrupt Reporting Mechanism Modes section for additional details of how the flags and INT pin are controlled. The master can obtain information about the source of the OPT3002 interrupt from the address broadcast in the above process. The flag high field (configuration register, bit 6) is sent as the final LSB of the address to provide the master additional information about the cause of the OPT3002 interrupt. If the master requires additional information, then the result register or the configuration register can be queried. The flag high and flag low fields are not cleared upon an SMBus alert response.
7.6 Register Maps
7.6.1 Internal Registers
The device is operated over the I2C bus with registers that contain configuration, status, and result information. All registers are 16 bits long.
There are four main registers: result, configuration, low-limit, and high-limit. There is also a manufacturer ID register. Table 6 lists these registers. Do not write or read registers that are not shown on this register map.
Table 6. Register Map
| REGISTER | ADDRESS (Hex) | 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Result | 00h | E3 | E2 | E1 | E0 | R11 | R10 | R9 | R8 | R7 | R6 | R5 | R4 | R3 | R2 | R1 | R0 |
| Configuration | 01h | RN3 | RN2 | RN1 | RN0 | CT | M1 | M0 | OVF | CRF | FH | FL | L | POL | ME | FC1 | FC0 |
| Low-limit | 02h | LE3 | LE2 | LE1 | LE0 | TL11 | TL10 | TL9 | TL8 | TL7 | TL6 | TL5 | TL4 | TL3 | TL2 | TL1 | TL0 |
| High-limit | 03h | HE3 | HE2 | HE1 | HE0 | TH11 | TH10 | TH9 | TH8 | TH7 | TH6 | TH5 | TH4 | TH3 | TH2 | TH1 | TH0 |
| Manufacturer ID | 7Eh | ID15 | ID14 | ID13 | ID12 | ID11 | ID10 | ID9 | ID8 | ID7 | ID6 | ID5 | ID4 | ID3 | ID2 | ID1 | ID0 |
7.6.1.1 Register Descriptions
7.6.1.1.1 Result Register (address = 00h)
This register contains the result of the most recent light-to-digital conversion. This 16-bit register has two fields: a 4-bit exponent and a 12-bit mantissa.
| 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 |
| E3 | E2 | E1 | E0 | R11 | R10 | R9 | R8 |
| R-0h | R-0h | R-0h | R-0h | R-0h | R-0h | R-0h | R-0h |
| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
| R7 | R6 | R5 | R4 | R3 | R2 | R1 | R0 |
| R-0h | R-0h | R-0h | R-0h | R-0h | R-0h | R-0h | R-0h |
| LEGEND: R = Read only; -n = value after reset |
Table 7. Result Register Field Descriptions
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 15-12 | E[3:0] | R | 0h | Exponent.
These bits are the exponent bits. Table 8 provides further details. |
| 11-0 | R[11:0] | R | 000h | Fractional result.
These bits are the result in straight binary coding (zero to full-scale). |
Table 8. Result Register: Full-Scale Range (FSR) and LSB Size as a Function of Exponent Level
| E3 | E2 | E1 | E0 | FSR AT 505-nm WAVELENGTH (nW/cm2) |
LSB WEIGHT AT 505-nm WAVELENGTH (nW/cm2) |
|---|---|---|---|---|---|
| 0 | 0 | 0 | 0 | 4,914 | 1.2 |
| 0 | 0 | 0 | 1 | 9,828 | 2.4 |
| 0 | 0 | 1 | 0 | 19,656 | 4.8 |
| 0 | 0 | 1 | 1 | 39,312 | 9.6 |
| 0 | 1 | 0 | 0 | 78,624 | 19.2 |
| 0 | 1 | 0 | 1 | 157,248 | 38.4 |
| 0 | 1 | 1 | 0 | 314,496 | 76.8 |
| 0 | 1 | 1 | 1 | 628,992 | 153.6 |
| 1 | 0 | 0 | 0 | 1,257,984 | 307.2 |
| 1 | 0 | 0 | 1 | 2,515,968 | 614.4 |
| 1 | 0 | 1 | 0 | 5,031,936 | 1,228.8 |
| 1 | 0 | 1 | 1 | 10,063,872 | 2,457.6 |
The formula to translate this register into optical power is given in Equation 1:
where
- LSB_Size = 2E[3:0] × 1.2 [nW/cm2]
LSB_Size can also be taken from Table 8. The complete optical power equation is shown in Equation 2:
A series of result register output examples with the corresponding LSB weight and resulting optical power are given in Table 9. Note that many combinations of exponents (E[3:0]) and fractional results (R[11:0]) can map onto the same optical power result, as shown in the examples of Table 9.
Table 9. Examples of Decoding the Result Register into Optical Power
| RESULT REGISTER (Bits 15-0, Binary) |
EXPONENT (E[3:0], Hex) |
FRACTIONAL RESULT (R[11:0], Hex) |
LSB WEIGHT AT 505-nm WAVELENGTH (nW/cm2, Decimal) |
RESULTING OPTICAL POWER AT 505-nm WAVELENGTH (nW/cm2, Decimal) |
|---|---|---|---|---|
| 0000 0000 0000 0001b | 00h | 001h | 1.2 | 1.2 |
| 0000 1111 1111 1111b | 00h | FFFh | 1.2 | 4,914 |
| 0011 0100 0101 0110b | 03h | 456h | 9.6 | 338,227.2 |
| 0111 1000 1001 1010b | 07h | 89Ah | 153.6 | 629,145.6 |
| 1000 1000 0000 0000b | 08h | 800h | 307.2 | 629,145.6 |
| 1001 0100 0000 0000b | 09h | 400h | 614.4 | 629,145.6 |
| 1010 0010 0000 0000b | 0Ah | 200h | 1228.8 | 629,145.6 |
| 1011 0001 0000 0000b | 0Bh | 100h | 2457.6 | 629,145.6 |
| 1011 0000 0000 0001b | 0Bh | 001h | 2457.6 | 2457.6 |
| 1011 1111 1111 1111b | 0Bh | FFFh | 2457.6 | 10,063,872 |
To compensate for the spectral response of the device, for input wavelengths other than 505 nm, see the Compensation for the Spectral Response section.
Note that the exponent field can be disabled (set to zero) by enabling the exponent mask (configuration register, ME field = 1) and manually programming the full-scale range (configuration register, RN[3:0] < 1100b (0Ch)), allowing for simpler operation in a manually-programmed, full-scale mode. Calculating optical power from the result register contents only requires multiplying the result register by the LSB weight (in nW/cm2) associated with the specific programmed full-scale range (see Table 8). See the low-limit register for details.
See the configuration register conversion time field (CT, bit 11) description for more information on optical power measurement resolution as a function of conversion time.
7.6.1.1.2 Configuration Register (address = 01h) [reset = C810h]
This register controls the major operational modes of the device. This register has 11 fields, as documented in this section. If a measurement conversion is in progress when the configuration register is written, then the active measurement conversion immediately aborts. If the new configuration register directs a new conversion, then that conversion is subsequently started.
| 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 |
| RN3 | RN2 | RN1 | RN0 | CT | M1 | M0 | OVF |
| R/W-1h | R/W-1h | R/W-0h | R/W-0h | R/W-1h | R/W-0h | R/W-0h | R-0h |
| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
| CRF | FH | FL | L | POL | ME | FC1 | FC0 |
| R-0h | R-0h | R-0h | R/W-1h | R/W-0h | R/W-0h | R/W-0h | R/W-0h |
| LEGEND: R/W = Read/Write; R = Read only; -n = value after reset |
Table 10. Configuration Register Field Descriptions
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 15-12 | RN[3:0] | R/W | 0Ch | Range number field (read or write).
The range number field selects the full-scale optical power range of the device. The format of this field is the same as the result register exponent field (E[3:0]); see Table 8. When RN[3:0] is set to 1100b (0Ch), the device operates in automatic full-scale setting mode, as described in the Automatic Full-Scale Setting Mode section. In this mode, the automatically chosen range is reported in the result exponent (register 00h, E[3:0]). The device powers up as 1100 in automatic full-scale setting mode. Codes 1101b, 1110b, and 1111b (0Dh, 0Eh, and 0Fh) are reserved for future use. |
| 11 | CT | R/W | 1h | Conversion time field (read or write).
The conversion time field determines the length of the light-to-digital conversion process. The choices are 100 ms and 800 ms. A longer integration time allows for a lower noise measurement. The conversion time also relates to the effective resolution of the data conversion process. The 800-ms conversion time allows for the fully specified optical power resolution. The 100-ms conversion time with full-scale ranges above 0101b for E[3:0] in the result and configuration registers also allows for the fully specified optical power resolution. The 100-ms conversion time with full-scale ranges below and including 0101b for E[3:0] can reduce the effective result resolution by up to three bits, as a function of the selected full-scale range. Range 0101b reduces by one bit. Ranges 0100b, 0011b, 0010b, and 0001b reduce by two bits. Range 0000b reduces by three bits. The result register format and associated LSB weight does not change as a function of the conversion time. 0 = 100 ms 1 = 800 ms |
| 10-9 | M[1:0] | R/W | 0h | Mode of conversion operation field (read or write).
The mode of conversion operation field controls whether the device is operating in continuous conversion, single-shot, or low-power shutdown mode. The default is 00b (shutdown mode), such that upon power-up, the device only consumes an operational level of power after appropriately programming the device. When single-shot mode is selected by writing 01b to this field, the field continues to read 01b when the device is actively converting. When the single-shot conversion is complete, the mode of conversion operation field is automatically set to 00b and the device is shut down. When the device enters shutdown mode, either by completing a single-shot conversion or by a manual write to the configuration register, there is no change to the state of the reporting flags (conversion ready, flag high, flag low) or the INT pin. These signals are retained for subsequent read operations when the device is in shutdown mode. 00 = Shutdown (default) 01 = Single-shot 10, 11 = Continuous conversions |
| 8 | OVF | R | 0h | Overflow flag field (read-only).
The overflow flag field indicates when an overflow condition occurs in the data conversion process, typically because the light illuminating the device exceeds the programmed full-scale range of the device. Under this condition OVF is set to 1, otherwise OVF remains at 0. The field is reevaluated on every measurement. If the full-scale range is manually set (RN[3:0] field < 1100b), the overflow flag field can be set when the result register reports a value less than full-scale. This result occurs if the input light has a temporary high spike level that temporarily overloads the integrating ADC converter circuitry but returns to a level within range before the conversion is complete. Thus, the overflow flag reports a possible error in the conversion process. This behavior is common to integrating-style converters. If the full-scale range is automatically set (RN[3:0] field = 1100b), the only condition that sets the overflow flag field is if the input light is beyond the full-scale level of the entire device. When there is an overflow condition and the full-scale range is not at maximum, the OPT3002 aborts the current conversion, sets the full-scale range to a higher level, and starts a new conversion. The flag is set at the end of the process. This process repeats until there is either no overflow condition or until the full-scale range is set to its maximum range. |
| 7 | CRF | R | 0h | Conversion ready field (read-only).
The conversion ready field indicates when a conversion completes. The field is set to 1 at the end of a conversion and is cleared (set to 0) when the configuration register is subsequently read or written with any value except for one containing the shutdown mode (mode of operation field, M[1:0] = 00b). Writing a shutdown mode does not affect the state of this field; see the Interrupt Reporting Mechanism Modes section for more details. |
| 6 | FH | R | 0h | Flag high field (read-only).
The flag high field (FH) identifies that the result of a conversion is larger than a specified level of interest. FH is set to 1 when the result is larger than the level in the high-limit register (register address 03h) for a consecutive number of measurements defined by the fault count field (FC[1:0]). See the Interrupt Reporting Mechanism Modes section for more details on clearing and other behaviors of this field. |
| 5 | FL | R | 0h | Flag low field (read-only).
The flag low field (FL) identifies that the result of a conversion is smaller than a specified level of interest. FL is set to 1 when the result is smaller than the level in the low-limit register (register address 02h) for a consecutive number of measurements defined by the fault count field (FC[1:0]). See the Interrupt Reporting Mechanism Modes section for more details on clearing and other behaviors of this field. |
| 4 | L | R/W | 1h | Latch field (read or write).
The latch field controls the functionality of the interrupt reporting mechanisms: the INT pin, the flag high field (FH), and flag low field (FL). This bit selects the reporting style between a latched window-style comparison and a transparent hysteresis-style comparison. 0 = The device functions in transparent hysteresis-style comparison operation, where the three interrupt reporting mechanisms directly reflect the comparison of the result register with the high- and low-limit registers with no user-controlled clearing event. See the Interrupt Operation, INT Pin, and Interrupt Reporting Mechanisms section for further details. 1 = The device functions in latched window-style comparison operation, latching the interrupt reporting mechanisms until a user-controlled clearing event. |
| 3 | POL | R/W | 0h | Polarity field (read or write).
The polarity field controls the polarity or active state of the INT pin. 0 = The INT pin reports active low, pulling the pin low upon an interrupt event. 1 = Operation of the INT pin is inverted, where the INT pin reports active high, becoming high impedance and allowing the INT pin to be pulled high upon an interrupt event. |
| 2 | ME | R/W | 0h | Mask exponent field (read or write).
The mask exponent field forces the result register exponent field (register 00h, bits E[3:0]) to 0000b when the full-scale range is manually set, which can simplify the processing of the result register when the full-scale range is manually programmed. This behavior occurs when the mask exponent field is set to 1 and the range number field (RN[3:0]) is set to less than 1100b. Note that the masking is only performed on the result register. When using the interrupt reporting mechanisms, the result comparison with the low-limit and high-limit registers is unaffected by the ME field. |
| 1-0 | FC[1:0] | R/W | 0h | Fault count field (read or write).
The fault count field instructs the device as to how many consecutive fault events are required to trigger the interrupt reporting mechanisms: the INT pin, the flag high field (FH), and flag low field (FL). The fault events are described in the latch field (L), flag high field (FH), and flag low field (FL) descriptions. 00 = One fault count (default) 01 = Two fault counts 10 = Four fault counts 11 = Eight fault counts |
7.6.1.1.3 Low-Limit Register (address = 02h) [reset = C0000h]
This register sets the lower comparison limit for the interrupt reporting mechanisms: the INT pin, the flag high field (FH), and flag low field (FL), as described in the Interrupt Reporting Mechanism Modes section.
| 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 |
| LE3 | LE2 | LE1 | LE0 | TL11 | TL10 | TL9 | TL8 |
| R/W-0h | R/W-0h | R/W-0h | R/W-0h | R/W-0h | R/W-0h | R/W-0h | R/W-0h |
| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
| TL7 | TL6 | TL5 | TL4 | TL3 | TL2 | TL1 | TL0 |
| R/W-0h | R/W-0h | R/W-0h | R/W-0h | R/W-0h | R/W-0h | R/W-0h | R/W-0h |
| LEGEND: R/W = Read/Write; -n = value after reset |
Table 11. Low-Limit Register Field Descriptions
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 15-12 | LE[3:0] | R/W | 0h | Exponent.
These bits are the exponent bits. Table 12 provides further details. |
| 11-0 | TL[11:0] | R/W | 000h | Result.
These bits are the result in straight binary coding (zero to full-scale). |
The format of this register is nearly identical to the format of the result register. The low-limit register exponent (LE[3:0]) is similar to the result register exponent (E[3:0]). The low-limit register result (TL[11:0]) is similar to the result register result (R[11:0]).
The equation to translate this register into the optical power threshold is given in Equation 3, which is similar to the equation for the result register, Equation 2.
Table 12 gives the full-scale range and LSB size of the low-limit register. The detailed discussion and examples given for the result register apply to the low-limit register as well.
Table 12. Low Limit Register: Full-Scale Range (FSR) and LSB Size as a Function of Exponent Level
| LE3 | LE2 | LE1 | LE0 | FSR AT 505-nm WAVELENGTH (nW/cm2) |
LSB WEIGHT AT 505-nm WAVELENGTH (nW/cm2) |
|---|---|---|---|---|---|
| 0 | 0 | 0 | 0 | 4,914 | 1.2 |
| 0 | 0 | 0 | 1 | 9,828 | 2.4 |
| 0 | 0 | 1 | 0 | 19,656 | 4.8 |
| 0 | 0 | 1 | 1 | 39,312 | 9.6 |
| 0 | 1 | 0 | 0 | 78,624 | 19.2 |
| 0 | 1 | 0 | 1 | 157,248 | 38.4 |
| 0 | 1 | 1 | 0 | 314,496 | 76.8 |
| 0 | 1 | 1 | 1 | 628,992 | 153.6 |
| 1 | 0 | 0 | 0 | 1,257,984 | 307.2 |
| 1 | 0 | 0 | 1 | 2,515,968 | 614.4 |
| 1 | 0 | 1 | 0 | 5,031,936 | 1,228.8 |
| 1 | 0 | 1 | 1 | 10,063,872 | 2,457.6 |
NOTE
The result and limit registers are all converted into optical power values internally for comparison. These registers can have different exponent fields. However, when using a manually-set, full-scale range (configuration register, RN < 0Ch, with mask enable (ME) active), programming the manually-set, full-scale range into the LE[3:0] and HE[3:0] fields can simplify the choice of programming the register. This simplification results in only having to consider the fractional result and not the exponent part of the result.
7.6.1.1.4 High-Limit Register (address = 03h) [reset = BFFFh]
The high-limit register sets the upper comparison limit for the interrupt reporting mechanisms: the INT pin, the flag high field (FH), and flag low field (FL), as described in the Interrupt Operation, INT Pin, and Interrupt Reporting Mechanisms section. The format of this register is almost identical to the format of the low-limit register and the result register. To explain the similarity in more detail, the high-limit register exponent (HE[3:0]) is similar to the low-limit register exponent (LE[3:0]) and the result register exponent (E[3:0]). The high-limit register result (TH[11:0]) is similar to the low-limit result (TH[11:0]) and the result register result (R[11:0]). Note that the comparison of the high-limit register with the result register is unaffected by the ME bit.
When using a manually-set, full-scale range with the mask enable (ME) active, programming the manually-set, full-scale range into the HE[3:0] bits can simplify the choice of values required to program into this register. The formula to translate this register into optical power is similar to Equation 3. The full-scale values are similar to Table 8.
| 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 |
| HE3 | HE2 | HE1 | HE0 | TH11 | TH10 | TH9 | TH8 |
| R/W-0h | R/W-0h | R/W-0h | R/W-0h | R/W-0h | R/W-0h | R/W-0h | R/W-0h |
| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
| TH7 | TH6 | TH5 | TH4 | TH3 | TH2 | TH1 | TH0 |
| R/W-0h | R/W-0h | R/W-0h | R/W-0h | R/W-0h | R/W-0h | R/W-0h | R/W-0h |
| LEGEND: R/W = Read/Write; -n = value after reset |
Table 13. High-Limit Register Field Descriptions
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 15-12 | HE[3:0] | R/W | Bh | Exponent.
These bits are the exponent bits. |
| 11-0 | TH[11:0] | R/W | FFFh | Result.
These bits are the result in straight binary coding (zero to full-scale). |
7.6.1.1.5 Manufacturer ID Register (address = 7Eh) [reset = 5449h]
This register is intended to help identify the device.
| 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 |
| ID15 | ID14 | ID13 | ID12 | ID11 | ID10 | ID9 | ID8 |
| R-0h | R-0h | R-0h | R-0h | R-0h | R-0h | R-0h | R-0h |
| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
| ID7 | ID6 | ID5 | ID4 | ID3 | ID2 | ID1 | ID0 |
| R-0h | R-0h | R-0h | R-0h | R-0h | R-0h | R-0h | R-0h |
| LEGEND: R = Read only; -n = value after reset |
Table 14. Manufacturer ID Register Field Descriptions
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 15-0 | ID[15:0] | R | 5449h | Manufacturer ID.
The manufacturer ID reads 5449h. In ASCII code, this register reads TI. |