Skip to content
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

Sending IR data rather than white-light data #38

Closed
terrillmoore opened this issue Jul 3, 2018 · 2 comments
Closed

Sending IR data rather than white-light data #38

terrillmoore opened this issue Jul 3, 2018 · 2 comments
Assignees
Labels

Comments

@terrillmoore
Copy link
Member

terrillmoore commented Jul 3, 2018

This is set up here:

gSi1133.configure(0, CATENA_SI1133_MODE_SmallIR);
gSi1133.configure(1, CATENA_SI1133_MODE_White);
gSi1133.configure(2, CATENA_SI1133_MODE_UV);

This means that the first entry is "small IR". We don't want small IR as the LUX reading, we want "white" as the Lux reading.

And, in fact, this "lux sensor" is not a lux sensor, it is a W/m^2 sensor. Lux needs to be compensated for frequency. It's possible that the SI1133 does this, but it's not obvious from the datasheet. See http://www.physlink.com/Education/AskExperts/ae409.cfm for more info.

First change is to transmit element [1] rather than [0]. Second is to possibly linearize, and third is to possibly change to a proper Lux sensor .

In any case, it is a big error to transmit this with the same data format as Rohm light output, because the engineering units are not commensurate. See #39.

@chwon64
Copy link
Contributor

chwon64 commented Jul 3, 2018

I changed transmit element from [0] to [1] and committed this change.
I am not sure how it linearize at this moment.

@terrillmoore
Copy link
Member Author

Closed by 1df74bc

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants