04-30-2021 12:24 PM
@NIquist wrote:
BTW, the header in the original file indicates that the curve is an optical response to light in the visible range (plus a bit into the IR). The light intensity is in micro-amps though which is meaningless without knowing how much optical power (in mW or dBm) that represents.
Hello,
can I ask you (for my general culture...) what mean... "a bit to IR" ?! I search this frontier for some years... and don't find it... and... only... the light intensity is in... micro-amps?! the electromagnetic radiation... are not in... "micro-amps" ?! or... only the... electromagnetic radiation are in W and... the light intensity are in... dB/m ??? I do not understand... nothing...
here I'm loosed.
can you... iluminate me ?!
04-30-2021 12:54 PM - edited 04-30-2021 12:55 PM
@xipxid wrote:
what mean... "a bit to IR" ?!
As was said, the spectrum is mostly in the visible range (defined as 400-750nm) so a "bit of IR" mean that the upper limit is slightly above 750nm (~800nm in this case). If it would go slightly below 400nm, it would have a bit of UV. Right?
The sensor outputs microamps and that can be converted to real units after calibration. Nothing to do with the final results.
None of this has anything to do with the original question or with LabVIEW. There are probably better places to ask these kinds of questions.
04-30-2021 01:39 PM
@altenbach wrote:
@NIquist wrote:
Your data file is not formatted correctly. There is no delimiter between the X and Y data.
The delimiter is a single <space> character and wiring that correctly to the current read function is all that's needed. 🙂
Yes indeed, you are correct! Of course a space character is a perfectly valid delimiter. I should have realized that. 🙄