<html><head><meta name="qrichtext" content="1" /></head><body style="font-size:11pt;font-family:Times">
<p>Hi,</p>
<p>notes about questions are interlaced.</p>
<p></p>
<p>On Saturday 19 February 2005 01:24, Jasem Mutlaq wrote:</p>
<p>> ----- Original Message -----</p>
<p>> From: "Gaetano Vocca" <yagvoc-web@yahoo.it></p>
<p>> To: "KStars Development Mailing List" <kstars-devel@kde.org></p>
<p>> Sent: Saturday, February 19, 2005 3:03 AM</p>
<p>> Subject: Re: [Kstars-devel] FLI CCD indi control panel</p>
<p>></p>
<p>> >I have just tested the FLI CCD driver a little bit after upgrading the cvs</p>
<p>> > and:</p>
<p>> > 1) In the Expose tab both the temperature slider and the edit box are now</p>
<p>> > independent from the current temperature of the camera, it's ok to me</p>
<p>> > (thank</p>
<p>> > you Jasem).</p>
<p>> > 2) Still in the Expose tab about the Duration fields. When the INDI</p>
<p>> > Control</p>
<p>> > panel is run the first time, the label (fourth control from left) shows</p>
<p>> > 1.00.</p>
<p>> > If I take a picture without filling the text box aside, the frame is 1</p>
<p>> > sec long and in the log window the message is "Taking a 1 seconds frame".</p>
<p>> > At this</p>
<p>> > point the label changes to 0.00.</p>
<p>> > If I take a second frame still without filling the text field, in the log</p>
<p>> > window the message is "Taking a 0 seconds frame" while the exposure is</p>
<p>> > still</p>
<p>> > 1 second long.</p>
<p>></p>
<p>> Hmmmm, okay, I'll check this problem out.</p>
<p>></p>
<p>> > 3) The driver needs, as supposed, to be run as root to properly connect</p>
<p>> > to the</p>
<p>> > camera due to the privileges of the usb device of the camera itself</p>
<p>> ></p>
<p>> > A very minor little note: as far as I know, for a Bias type of exposure</p>
<p>> > the</p>
<p>> > duration is unuseful because this should be anyway the shortest exposure</p>
<p>> > possible for the given sensor.</p>
<p>></p>
<p>> True. But from the FLI manual, the shortest possible exposure is 50 ms, so</p>
<p>> it's specified as that.</p>
<p>You are right so, actually, the content of the Duration field is not so significant. Would it be possible to disable the Duration when Bias exposure is selected? I don't know the impact on the code, if it's too high don't worry. </p>
<p>></p>
<p>> > If you have any suggestion for any test I can perform, don't hesitate to</p>
<p>> > tell</p>
<p>> > me, I will try.</p>
<p>></p>
<p>> Yes. Were you able to capture frames without problems? Was the frame sent</p>
<p>> to KStars and displayed properly? What happens when you run the driver as a</p>
<p>> user? what's the error messages you get?</p>
<p></p>
<p>Yas, I am able to take light frames without problem and they are correctly displayed in the FITS viewer. They are not so nice because the camera is not currently plugged to a telescope but everything seems to work flawlessly.</p>
<p>About the "user mode". Here the issue is that the library from FLI needs to open the USB devices to check for the presence of the camera and to talk to it. When not run as root it is impossible for the library to open the device, here follow some lines from /var/log/messages</p>
<p></p>
<p><span style="font-family:Courier [Adobe]">...</span></p>
<p><span style="font-family:Courier [Adobe]">Feb 19 12:29:17 numenor fliccd: Entering FLIOpen()</span></p>
<p><span style="font-family:Courier [Adobe]">Feb 19 12:29:17 numenor fliccd: Trying to open file </proc/bus/usb/001/001> in domain 258.</span></p>
<p><span style="font-family:Courier [Adobe]">Feb 19 12:29:17 numenor fliccd: Got device index 0</span></p>
<p><span style="font-family:Courier [Adobe]">Feb 19 12:29:17 numenor fliccd: Domain: 0x0002</span></p>
<p><span style="font-family:Courier [Adobe]">Feb 19 12:29:17 numenor fliccd: Type: 0x0100</span></p>
<p><span style="font-family:Courier [Adobe]">Feb 19 12:29:17 numenor fliccd: fli_connect() error -13 [Permission denied]</span></p>
<p><span style="font-family:Courier [Adobe]">...</span></p>
<p></p>
<p>So the indi driver cannot do anything but returning "Error: no cameras were detected." in the log window.</p>
<p>Actually I am having some troubles with the FLI library related to the USB handling that I worked around with some tricks. I didn't write about them thinking that it is a little bit off-topic in this list but if you are interested I'll be happy to tell you.</p>
<p> </p>
<p>></p>
<p><span style="color:#008000">> Thanks a lot for testing this driver Gaetano :-)</span></p>
<p><span style="color:#008000">></span></p>
<p><span style="color:#008000">> Good luck,</span></p>
<p><span style="color:#008000">> Jasem</span></p>
<p><span style="color:#008000">></span></p>
<p></p>
<p>It is nothing if compared to the work that all of you have done with kstars.</p>
<p></p>
<p>Cheers,</p>
<p>Gaetano</p>
<p></p>
<p>PS: What about thinking a little bit to supporting the filter wheel? It shouldn't be too hard and, if I can help, I'm ready :-)</p>
<p></p>
</body></html>