[argyllcms] Re: Meter autodetection upsets Lumagen scaler on serial port
- From: James Finnie <james@xxxxxxxxxxxxxxx>
- To: argyllcms@xxxxxxxxxxxxx
- Date: Thu, 27 Oct 2016 22:15:40 +0100
Thanks for the reply Graeme.
what sort of serial port are you using to the Lumagen ?
(I'm guessing it's a USB to serial adapter...)
FTDI based USB serial converter.
What sort of problems does it cause ?
I initially thought it was just throwing up the status screen on the
Lumagen. However I now realised after some measurements settings that
I couldn't quite get my head around, I realised that other things can
happen - like changing inputs (the numbers would cause that), output
resolution, and I'm pretty sure I've seen it change memories too
(which can result in different CMS settings being loaded) - though not
totally sure how that could have happened from the string you listed.
It's going to be painful if the Lumagen reacts to single characters, which
is what you are implying. The only thing Argyll does when fast
scanning a port is send it the string ";D024\r\n". It won't do any
more than that if it doesn't get a recognizable response.
This is the case. By default echo is turned on I believe, and trying
the sequence you list doesn't seem to elicit any non-echo response.
The Lumagen has 4 different communication configurations, and I think
that it's only one of those that tries to respond to each character
rather than wait for a full line of input. So in theory setting any of
those other modes (Delimeters On, or Delimeters On with Ack/Nack, or
Delimeters On with Checsum and Ack/Nack) should prevent side effects.
I have no idea whether other software that talks to the Lumagen
is smart enough to cope with these modes though.
Unfortunately neither Lightspace nor Chromapure can communicate with
the unit in any of these alternative modes.
Other related posts: