I've found that dealing directly with hardware and reading registers yourself can be tedious and frustrating, especially when it's difficult to find reference points (testing lux is definitely one of these times, as someone across the 'net may have several 1kW bulbs burning, but their bulbs may have x, or y, or z or any number of other spectrum-diffusing things happening).
I'm glad the recommendation for an app helped. After my units arrive, I'll drum up some code being non-biased, and we can compare some numbers (again though, I'm sure my light source'll be different from yours. However, there's always one that is pretty consistent ;)
I often write C against my Arduino that has analog inherent, then translate the C code to something I can provide a Perl API for, so I get results on two separate platforms (for instance, my ADCs/dpots I test against the Arduino, then port to the Rasperry Pi). I'm looking forward to getting these units so I can have someone live-time to compare numbers with and discuss.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
