[argyllcms] Re: Image Engineering EX1 Spectroradiometer
- From: "Richard Kirk" <dmarc-noreply@xxxxxxxxxxxxx> (Redacted sender "richard" for DMARC)
- To: argyllcms@xxxxxxxxxxxxx
- Date: Wed, 19 Feb 2020 19:06:32 +0000
On 19 Feb 2020, at 17:05, Cody Ranaldo <lessbones@xxxxxxxxx> wrote:
It would be pretty great if FilmLight were willing to release that code and
it could be added to argyll—
I am asking whether I can do this with the Powers That Be. I don’t see why they
shouldn’t agree. I can do a bit of work on this just so it compiles, but I am
hoping to do little more than that. Argyll will have to have somewhere where
they would be willing for this stuff to live. But first let’s just check what
these things do, in case you don’t want it…
Here, for example, is info message from the JETI tool ’specbos’
specbos -i
specbos [options] [commands]
This sets the options, then interacts with the spectrometer,
taking commands from the command line, then from a prompt.
options:
f=%s : output file name (default Jeti Specbos)
p=%s : specbos serial port (default (null))
-h -i : help/info (this is it)
-e : echo monitor I/O messages (-ee for hex escapes)
-p : disable Jeti Specbos parameter set-up
-s : save file after each measurement (default: no automatic save)
-t : Take commands from /tmp/tl-meter/command.
Jeti Specbos commands...
? : Help menu (this is it)
-e : Toggle serial echo mode on|off
-s : Toggle save file after measurement on|off
-q : Quiet mode (suppress comments)
(ret) or x : Measure point, print values
or o : Read spectrum from Jeti Specbos, save to file specbos.000
o:<file> : Read spectrum from Jeti Specbos, save to file <file>
f : Flush spectrometer output
*... : Send commands to spectrometer and wait for reply
You can run ’specbos’ and get it to execute the commands, and then exit, or you
can run ’specbos -t’ and it will look in /tmp/tl-meter/command for a command,
and write any reply to /tmp/tl-meter/reply. This is pretty ugly but it lets any
app send simple commands to the ’specbos’ driver using just the standard libs.
This allowed it to run on Linux, Windows, and Mac when that wasn’t easy to do.
The file commands are a standard set across all my drivers, while the
command-line commands are different for each device.
The commands are single letters..
T : return long timeout in seconds ( so you know when to give up )
V : return driver name and version ( which will yell you want it is connected
to )
X : return XYZ values or error string
S : return spectrum values or error string (not supported for colorimeters)
Q : Quit
Speaking of which, does anyone have some insight as to what is actually done
when a device is recertified/calibrated? Is this usually performed through
some kind of proprietary software offsets? I've always opened these older
devices hoping for some array of trim-pots to start fiddling with, but never
such luck, and for current i1pro devices I can't imagine they're cracking
them open and changing out resistors and the like.
I used to do this for the Truelight monitor and projector probes. We had a
helium lamp which checked the wavelength in 5 points, a broadband tungsten lamp
for calibrating the sensitivity, and a tungsten reference for checking that. We
also had a reference display. With a new probe, I would measure the light
sources and the dark noise level, and a bunch of other things, and use this to
set up the calibration in EEPROM. We also used a moving spot on the monitor to
check the optics were aligned with the laser pointer. If everything checked
out, then life was pretty easy. If it turned out the dark noise was too high,
or the signal was too low, or the shutter as sticking, then we had to take it
to bits. This meant I had to have a dark room pretty much dedicated to doing
this sort of thing as you can’t pack it up and put it away, which at Central
London rates was not cheap.
Cheers
Richard
Other related posts:
