Hi. No. Mirror lockup is not necessary to be able to take an exposure.
If you're having trouble taking a shot, after changing for a cable which you know to work, make sure mirror lock is disabled both in camera and disabled and in indi.
Cheers and HTH.
Is this what is supposed to happen?
kstars - settings - configure kstars - EKOS
A search on 'cypress chipsets usb' should throw it up. I always had difficulty finding it so when I had it working, I saved a copy.
I have only tested it on Ubuntu on a Dell laptop. The reason we needed it is that we didn't have a spare usb2 port. You can choose which zwo model you have on the command line when you update the firmware.
HTH and clear skeis
120mm stable and reliable on any usb port with this firmware:
tested with ubuntu 18.04
Cheers and HTH
Is the loop thing where you connect the mount to a copper pipe hammered into wet ground?
Hi everyone and thanks for all the suggestions.
I traced it to the hub, but not what you'd expect. I removed the power from the hub and it now works reliably every time. Not seen that posted before so I hope others may benefit.
I've a DSLR, a zwo guide camera and an eq6.
If there's anything to test, please do say when it hits git. I'd be only too pleased to try it out.
It changed to:
An advice piece: "Things I've learned, while learning KStars/Ekos/INDI"
Now it's back to normal.
knro wrote: This is odd.. what was the original title for this thread?
'lost guide star: scheduler does not recover'
Currently PHD2 decides when to give up. If this happens, it gets 5 retries. When these fail, the job gets aborted.
Now it's even more confusing!
The title of the thread was changed and I couldn't find it any longer. I had to search.
So, not sure if I need to answer this but in my case, even when PHD2 confirmed the star was lost, the scheduler did not recover.
**Please could we retain the thread title or at least tell the OP if moderated otherwise? Thanks.
Why has the title of my thread been changed?
Ahhgghh... It's just taken me an hour to find 'remember job progress' I'm being super stupid today!!!
Anyway, as I understand, my issue was an exception; the repeat the same job every hour is a workaround?
The idea of aborting on error and then having the scheduler recover via align, guide and capture (which worked well a few weeks ago) would get my vote.
I really appreciate your help and understanding.