Hello indi people,
I have an old webcam Philips SPC 900 NC I have modified for long exposure using the led control (so called lxled mod).
I was using it for quite some time with indi and was happy about it despite I had to happy a rather ugly patch to the indi-v4l2-ccd driver to make it work. The patch can be found in this thread: www.indilib.org/forum/development/8752-i...borting-capture.html
I recently upgraded indi to 1.9.8 re-applied my patch and installed but then the long exposure mode stopped working when trying to start exposing in php2 (loop mode) I get the message below (translated from french):
Unsupported type or read error when loading FITS fileAnd the loop stops here. No other error from the console where indiserver runs:
indiserver -v indi_v4l2_ccd indi_simulator_telescope ✘ INT 1m 55s
2024-05-16T22:02:21: startup: indiserver -v indi_v4l2_ccd indi_simulator_telescope
2024-05-16T22:02:21: Driver indi_v4l2_ccd: pid=507965 rfd=6 wfd=6 efd=7
2024-05-16T22:02:21: Driver indi_simulator_telescope: pid=507966 rfd=8 wfd=8 efd=9
2024-05-16T22:02:21: listening to port 7624 on fd 5
2024-05-16T22:02:21: Local server: listening on local domain at: @/tmp/indiserver
2024-05-16T22:02:21: Driver indi_simulator_telescope: HaAxis: TrackRate 1, trackingRateDegSec 15.041067 arcsec
2024-05-16T22:02:21: Driver indi_v4l2_ccd: Using default decoder 'Builtin decoder'
2024-05-16T22:02:21: Driver indi_v4l2_ccd: Supported V4L2 formats are:
2024-05-16T22:02:21: Driver indi_v4l2_ccd: Y16
2024-05-16T22:02:21: Driver indi_v4l2_ccd: NV21
2024-05-16T22:02:21: Driver indi_v4l2_ccd: BA81
2024-05-16T22:02:21: Driver indi_v4l2_ccd: YU12
2024-05-16T22:02:21: Driver indi_v4l2_ccd: NV12
2024-05-16T22:02:21: Driver indi_v4l2_ccd: YV12
2024-05-16T22:02:21: Driver indi_v4l2_ccd: BYR2
2024-05-16T22:02:21: Driver indi_v4l2_ccd: RGB3
2024-05-16T22:02:21: Driver indi_v4l2_ccd: RGGB
2024-05-16T22:02:21: Driver indi_v4l2_ccd: GRBG
2024-05-16T22:02:21: Driver indi_v4l2_ccd: JPEG
2024-05-16T22:02:21: Driver indi_v4l2_ccd: MJPG
2024-05-16T22:02:21: Driver indi_v4l2_ccd: RGBO
2024-05-16T22:02:21: Driver indi_v4l2_ccd: RGBP
2024-05-16T22:02:21: Driver indi_v4l2_ccd: YVYU
2024-05-16T22:02:21: Driver indi_v4l2_ccd: YUYV
2024-05-16T22:02:21: Driver indi_v4l2_ccd: GREY
2024-05-16T22:02:21: Driver indi_v4l2_ccd: VYUY
2024-05-16T22:02:21: Driver indi_v4l2_ccd: UYVY
2024-05-16T22:02:21: Driver indi_simulator_telescope: snooping on GPS Simulator.GEOGRAPHIC_COORD
2024-05-16T22:02:21: Driver indi_simulator_telescope: snooping on GPS Simulator.TIME_UTC
2024-05-16T22:02:21: Driver indi_simulator_telescope: snooping on Dome Simulator.DOME_PARK
2024-05-16T22:02:21: Driver indi_simulator_telescope: snooping on Dome Simulator.DOME_SHUTTER
2024-05-16T22:02:21: Driver indi_v4l2_ccd: snooping on Telescope Simulator.EQUATORIAL_EOD_COORD
2024-05-16T22:02:21: Driver indi_v4l2_ccd: snooping on Telescope Simulator.EQUATORIAL_COORD
2024-05-16T22:02:21: Driver indi_v4l2_ccd: snooping on Telescope Simulator.TELESCOPE_INFO
2024-05-16T22:02:21: Driver indi_v4l2_ccd: snooping on Telescope Simulator.GEOGRAPHIC_COORD
2024-05-16T22:02:21: Driver indi_v4l2_ccd: snooping on Telescope Simulator.TELESCOPE_PIER_SIDE
2024-05-16T22:02:21: Driver indi_v4l2_ccd: snooping on SQM.SKY_QUALITY
// When I connect using phd2 client
2024-05-16T22:02:41: Client 11: new arrival from 127.0.0.1:36214 - welcome!
2024-05-16T22:02:41: Driver indi_v4l2_ccd: VIDIOC_CROPCAP: Inappropriate ioctl for device
2024-05-16T22:02:41: Driver indi_v4l2_ccd: Decoder usesoftcrop true
2024-05-16T22:02:41: Driver indi_v4l2_ccd: VIDIOC_ENUM_FRAMEINTERVALS: Invalid argument
2024-05-16T22:02:41: Driver indi_v4l2_ccd: VIDIOC_ENUM_FRAMEINTERVALS: Invalid argument
2024-05-16T22:02:41: Driver indi_v4l2_ccd: VIDIOC_ENUM_FRAMEINTERVALS: Invalid argument
2024-05-16T22:02:41: Driver indi_v4l2_ccd: Decoder set format: YU12 size 320x240 bpp 8
2024-05-16T22:02:41: Driver indi_v4l2_ccd: Decoder: Colorspace is 8, using default ycbcr encoding and quantization
2024-05-16T22:02:41: Driver indi_v4l2_ccd: Decoder allocBuffers cropping false
2024-05-16T22:02:41: Driver indi_v4l2_ccd: Control Class User Controls
2024-05-16T22:02:41: Driver indi_v4l2_ccd: Control Brightness
2024-05-16T22:02:41: Driver indi_v4l2_ccd: integer
// enable the LXLED mode
2024-05-16T22:02:41: Driver indi_v4l2_ccd: Control Contrast
2024-05-16T22:02:41: Driver indi_v4l2_ccd: integer
2024-05-16T22:02:41: Driver indi_v4l2_ccd: Control Saturation
2024-05-16T22:02:41: Driver indi_v4l2_ccd: integer
2024-05-16T22:02:41: Driver indi_v4l2_ccd: Control White Balance, Automatic
2024-05-16T22:02:41: Driver indi_v4l2_ccd: Menu items:
2024-05-16T22:02:41: Driver indi_v4l2_ccd: Indoor (Incandescant Lighting)
2024-05-16T22:02:41: Driver indi_v4l2_ccd: Outdoor (Sunlight) Mode
2024-05-16T22:02:41: Driver indi_v4l2_ccd: Indoor (Fluorescent Lighting) M
2024-05-16T22:02:41: Driver indi_v4l2_ccd: Manual Mode
2024-05-16T22:02:41: Driver indi_v4l2_ccd: Auto Mode
2024-05-16T22:02:41: Driver indi_v4l2_ccd: Control Red Balance
2024-05-16T22:02:41: Driver indi_v4l2_ccd: integer
2024-05-16T22:02:41: Driver indi_v4l2_ccd: Control Blue Balance
2024-05-16T22:02:41: Driver indi_v4l2_ccd: integer
2024-05-16T22:02:41: Driver indi_v4l2_ccd: Control Gamma
2024-05-16T22:02:41: Driver indi_v4l2_ccd: integer
2024-05-16T22:02:41: Driver indi_v4l2_ccd: Control Exposure
2024-05-16T22:02:41: Driver indi_v4l2_ccd: integer
2024-05-16T22:02:41: Driver indi_v4l2_ccd: Control Gain, Automatic
2024-05-16T22:02:41: Driver indi_v4l2_ccd: boolean
2024-05-16T22:02:41: Driver indi_v4l2_ccd: Control Gain
2024-05-16T22:02:41: Driver indi_v4l2_ccd: integer
2024-05-16T22:02:41: Driver indi_v4l2_ccd: Control Backlight Compensation
2024-05-16T22:02:41: Driver indi_v4l2_ccd: boolean
2024-05-16T22:02:41: Driver indi_v4l2_ccd: Control Color Effects
2024-05-16T22:02:41: Driver indi_v4l2_ccd: Menu items:
2024-05-16T22:02:41: Driver indi_v4l2_ccd: None
2024-05-16T22:02:41: Driver indi_v4l2_ccd: Black & White
2024-05-16T22:02:41: Driver indi_v4l2_ccd: Control Band-Stop Filter
2024-05-16T22:02:41: Driver indi_v4l2_ccd: boolean
2024-05-16T22:02:41: Driver indi_v4l2_ccd: Control Auto contour
2024-05-16T22:02:41: Driver indi_v4l2_ccd: boolean
2024-05-16T22:02:41: Driver indi_v4l2_ccd: Control Contour
2024-05-16T22:02:41: Driver indi_v4l2_ccd: integer
2024-05-16T22:02:41: Driver indi_v4l2_ccd: Control Dynamic Noise Reduction
2024-05-16T22:02:41: Driver indi_v4l2_ccd: integer
2024-05-16T22:02:41: Driver indi_v4l2_ccd: Control Auto White Balance Speed
2024-05-16T22:02:41: Driver indi_v4l2_ccd: integer
2024-05-16T22:02:41: Driver indi_v4l2_ccd: Control Auto White Balance Delay
2024-05-16T22:02:41: Driver indi_v4l2_ccd: integer
2024-05-16T22:02:41: Driver indi_v4l2_ccd: Control Save User Settings
2024-05-16T22:02:41: Driver indi_v4l2_ccd: button
2024-05-16T22:02:41: Driver indi_v4l2_ccd: Control Restore User Settings
2024-05-16T22:02:41: Driver indi_v4l2_ccd: button
2024-05-16T22:02:41: Driver indi_v4l2_ccd: Control Restore Factory Settings
2024-05-16T22:02:41: Driver indi_v4l2_ccd: button
2024-05-16T22:02:41: Driver indi_v4l2_ccd: Control Class Flash Controls
2024-05-16T22:02:41: Driver indi_v4l2_ccd: Control Strobe
2024-05-16T22:02:41: Driver indi_v4l2_ccd: button
2024-05-16T22:02:41: Driver indi_v4l2_ccd: Control Stop Strobe
2024-05-16T22:02:41: Driver indi_v4l2_ccd: button
2024-05-16T22:02:42: Client 12: new arrival from 127.0.0.1:36222 - welcome!
// starting exposing in loop with a duration of 0.5s
2024-05-16T22:03:07: Driver indi_v4l2_ccd: Decoder reset crop
2024-05-16T22:03:07: Driver indi_v4l2_ccd: Decoder allocBuffers cropping false
2024-05-16T22:03:07: Driver indi_v4l2_ccd: setlexstate to 2
2024-05-16T22:03:07: Driver indi_v4l2_ccd: setlexstate to 0No error neither in the INDI console
Reverting to 1.9.7 makes the cam work again. After investigating a bit further I nailed down that particular commit: github.com/indilib/indi/commit/d3e668303...9e0e92f0680c4717e791
As it was introduced very late in this release I tried reverting it and the newly compiled package works nicely. However of course, further commits in 1.9.9 require that change and so I can't upgrade any further.
I took a look at the commit and on its own it just looks like fairly innocent change rename 2 functions and changing some of their arguments...
I have no idea why this messes up with the cam and I'm seeking for help fixing that. If possible I'd rather avoid another ugly patch so I'm more seeking for guidance/answers and better understand the problem, so I can hopefully try to fix it myself in the right way (despite my limited knowledge of C and hardware coding :-/ )
Let me know if specific information would be required
Read More...
Did you run ldconfig after renaming the symlink from /usr/local/lib/libqhyccd.so.20 to /usr/local/lib/libqhyccd.so.22?
Read More...
Hi Dan,
All previous frames were taken with the buffer already set to the 4096 max.
I have tried taking different frames bellow at 512, 2048 and 4096 but I can't see much difference.
Can you tell me more about this timing error and the qhy recommendation of using slow usb. I find it quite painful that I have to wait around 20s after the actual exposure and I really wonder why.
If I understand you correctly the dark (at least the slow one) is fine and the camera is working ok as long as I use the slow mode?
Read More...
Hello,I have a QHY-10 and I have to admit I'm not using it that often... (almost never)I just took it out of the cupboard a few days ago to test some stuff and took a deeper look at the camera and the darks I took with them.I'm no CCD expert, and I know that's a rather old cam but the darks look odd to me. When visualizing the dark frame in Siril and setting the display to linear it of course looks all black, but when setting it the display mode to auto-adjust I can see a gradient of colors from purple to green.More interesting, if I set the qhy_ccd driver to USB=1 of USB=0, the gradient direction moves from vertical to horizontal...Bellow are screenshots from both darks, in slow (~20s to get the frame) and fast (~1s to get the frame) modes:
Slow:
Fast:
I would be curious to understand:
* why am I getting different gradients depending on that setting of the qhy_ccd driver(USB speed)
* If that's something with the driver, what's the right way to configure the camera?
* Are these gradients normal or is it a proof of something wrong with my cam?
P.S: FITS are available fits darkshere
Read More...
Interestingly enough I figured out the latest SDK provided for Linux by QHY (at least the last one I found) ships a
.so.22.8.17.17.so.20That's probably a bug and you should rename that link to
.so.22All libs should be installed in /usr/local/lib which is a quite common location for manually installed software and most systems should look in this folders for files. So I would assume that simply renaming the file will fix the problem.
(Assuming you installed the library from the QHY SDK here)
Read More...
I've probably been too fast responding... I've done some more tests and can confirm I4ve seen same crashes.
First time Kstars notified about driver crash and restarted it. Then trying to take the next frame, Kstars crashed as a whole.
However after restarting the indiserver I can't reproduce it anymore
Read More...
Hi Dan,
Long time I didn't use my QHY-10! I took out of its box and tried it on my Debian:
* Debian GNU/Linux 11.4
* Kstars 3.6.1 Beta (compiled from sources)
* indi-qhy 2.7
* libqhy 22.7.23
Taking a preview image from the CCD tab worked for me. Also worked from the indi control panel.
Do you have any error message?
Read More...
Looks like something happened with my post. It now fails to display with the error you can see above: Rendering Error in layout Topic/Edit/History: array_keys(): Argument #1 ($array) must be of type array, null given. Please enable debug mode for more information.
Maybe it never really worked which could explain why nobody replied but I think it used to display nicely...
Any update on the forum?
Read More...
Basic Information
-
About me
New to astronomy. Linux user for 20 years or so