One question on using this driver. I have the QHY600M (i.e. mono). In the INDI control panel on the Image Info tab it shows under Bayer Info filter RGGB. Since this is a mono camera should I change this to something else?
I decided to switch to running kstars/ekos on the rPi4 rather than remote mode with iMac client. This was mainly driven by the fact that firecapture now runs native on Stellarmate with the new beta but it also means I don’t have to worry about the file transfer back to the client. In order to support high frame rate for firecapture I’m going to an NVMe ssd via usb so for non planetary imaging I can save to that (it’s a 1 TB ssd) as well and copy the files over via smb. I will use ASTAP on the iMac to live stack from the smb so I can monitor progress as I run things from the iMac via vnc. I upgraded to an 8GB rPi so between that and the improved disk size and performance it should work fine (once I sort out a power supply that lets the usb ssd run glitch free.
I got my QHY600 an 1x1 bin is working fine on Stellarmate 1.5.4 on rPi4. Haven’t tried iMac remote.
I’m going to go ahead and get one so will see if the transfer to Mac is also a problem. Not sure how long it will take to arrive.
It seems like it may not be the QHY driver since it is apparently an issue of server-client communication, as opposed to server-camera communication.
That makes it sound like it isn’t a usb issue?
What happens if you save the image remotely on the indi-server instead of locally on the windows client
Previously you had it working with kstars on rPi, did you try running kstars remotely from windows to rPi? Is this recent windows/Ubuntu problem with PC connected directly to camera via usb?
Was this problem figured out? I am thinking of buying a QHY600 but want to be sure it will work with my setup - Stellarmate on a rPi4 running remotely from an iMac.
With the fix that is now implemented auto focus is working correctly.
Last night 3.5.3 Mac beta crashed while imaging. The log doesn't reveal much:
[2021-05-05T01:14:05.291 MDT INFO ][ org.kde.kstars.ekos.capture] - "Guiding deviation 4.291 exceeded limit value of 4 arcsecs, suspending exposure and waiting for guider up to 60.000 seconds."
[2021-05-05T01:14:05.316 MDT INFO ][ org.kde.kstars.ekos.capture] - "CCD capture suspended"
[2021-05-05T01:14:05.332 MDT DEBG ][ org.kde.kstars.ekos] - Dark frame subtraction applied
[2021-05-05T01:14:06.753 MDT INFO ][ org.kde.kstars.ekos.capture] - "Guiding deviation 4.028 is still higher than limit value of 4 arcsecs."
[2021-05-05T01:14:06.768 MDT DEBG ][ org.kde.kstars.ekos] - Dark frame subtraction applied
[2021-05-05T01:14:08.367 MDT INFO ][ org.kde.kstars.ekos.capture] - "Guiding deviation 0.593 is now lower than limit value of 4 arcsecs, resuming exposure."
[2021-05-05T01:14:08.383 MDT DEBG ][ org.kde.kstars.ekos] - Dark frame subtraction applied
[2021-05-05T01:14:08.388 MDT INFO ][ org.kde.kstars.ekos.capture] - "Job requires 300.000-second LPR images, has 3/12 frames captured and will be processed."
[2021-05-05T01:14:08.402 MDT INFO ][ org.kde.kstars.ekos.capture] - "Waiting for guide drift below 2 a-s..."
[2021-05-05T01:14:09.606 MDT INFO ][ org.kde.kstars.ekos.capture] - "Capturing 300.000-second LPR image..."
[2021-05-05T01:14:09.623 MDT DEBG ][ org.kde.kstars.ekos] - Dark frame subtraction applied
[2021-05-05T01:14:10.540 MDT INFO ][ org.kde.kstars.indi] - Canon DSLR EOS R : "[INFO] Starting 300 seconds exposure. "
[2021-05-05T01:14:10.839 MDT DEBG ][ org.kde.kstars.ekos] - Dark frame subtraction applied
[2021-05-05T01:14:12.111 MDT DEBG ][ org.kde.kstars.ekos] - Dark frame subtraction applied
[2021-05-05T01:14:13.392 MDT DEBG ][ org.kde.kstars.ekos] - Dark frame subtraction applied
[2021-05-05T01:14:14.726 MDT DEBG ][ org.kde.kstars.ekos] - Dark frame subtraction applied
[2021-05-05T01:14:16.016 MDT DEBG ][ org.kde.kstars.ekos] - Dark frame subtraction applied
the dark frame subtracted message (from guiding repeats many time and then it all stops)
When I woke up it wasn't running, the guiding was having problems (poor seeing I think) but no particular reason it should have hung. The gradual increase in HFR isn't a kstars problem -o isn't working in new indilib for esatto focuser so I can't adjust for temperature change - I am loop ing a 12x5min sub using the sequencer with focus disabled.
Is there a simple way to go back to 1.8.9 for sensosesto/esatto since that version appears to work?
sent my teamviewer info to support
I seem to be having a similar problem (perhaps associated with indilib upgrading to 1.9 - it was working with 1.8?). I can focus by looping and manually changing the position but autofocus hangs after it states it is making the initial move. The indi control panel readout of the Esatto position seems odd as well. If you tel it to move to a new position it does but the position doesn't update in the panel. If you tell it to move again it does update to the new location. It apperas the focuser position isn't updating properly.