Actually, I think that was a stupid question. Half a turn sounds pretty huge.

Read More...

Thanks, Chris. Is 500 just an arbitrary number? Or in the ballpark of what you've been seeing? Just don't want to start my experiment in a completely wrong direction..

Read More...

Chris,

quick question: are there any instructions on how to correctly configure backlash?

Read More...

Mark,

in the past, calibration was only available via the Celestron SCT driver. As I don't use a Celestron mount anymore, I can't say whether that's still the case.
Can you connect the focuser directly (via USB) to your computer and try that?

Cheers
Boris

Read More...

Yes, I also thought the Mini was immune to those issues. Plus, there doesn’t even seem to be a compatible firmware I could flash to solve the issue.

Read More...

Alright, I've looked into the debug logs, this is what I am seeing repeatedly:

org.kde.kstars.indi: ZWO CCD ASI120MM Mini : "[DEBUG] StartExposure->setexp : 1.000s "
org.kde.kstars.indi: ZWO CCD ASI120MM Mini : "[DEBUG] ASIGetExpStatus failed. Restarting exposure... "
org.kde.kstars.indi: ZWO CCD ASI120MM Mini : "[DEBUG] StartExposure->setexp : 1.000s "

Read More...

Tried it right away because I had indeed used the USB3 ports. Unfortunately, that did not solve the problem

Read More...

I just got myself a ZWO ASI 120MM Mini for guiding, in addition to the ASI224 I already use. Both cameras show up in Ekos, but while the ASI 224 succesfully captures pictures, the ASI 120MM doesn't. For example, when trying to capture a preview, it does so in an endless loop without ever showing any image.

Any suggestions? I believe a compatibility firmware is not need for that one, so I really don't know where to start.

Thanks.

Read More...

Apologies. I took the screenshot the only time I tried the same thing with Saturn.

Independent of that: the coordinates in the two panels differ significantly. Why would that be?

Read More...

I must be doing something wrong, but I am not sure what it is. I was doing a Solar System Align on Jupiter with my Nexstar Evolution yesterday, then tried to switch over to Ekos. But when I try to align the mount to Jupiter over there, it moves the mount to some completely different place. For some reason, the coordinates that are coming from the mount to KStars seem to differ from the ones that are e.g. reported by SkySafari. See attachment.

Is there anything I am obviously doing wrong? I've connected the mount via USB to the HC, using the Celestron GPS driver.

Read More...

Thanks, Chris. I found a similar FAQ on the Celestron site last night but was too tired to answer my own question Still surprised they didn't put that directly into the manual for the wedge...

Read More...

I just bought myself a wedge for my Celestron Evolution mount. Trying it for the first time, I did the following:

• Performed a SolarSystem align in EQ North Mode, using the hand controller
• Connected INDI via Celestron GPS driver
• Driver shows EQ N as mode

You can give my script a try now. I have most of the issues all worked out. There are still just a couple of things that I want to refine, but nothing that should stop you

1. ZRam is awesome. It does cost a little in cpu cycles, but it doesn't hurt the sd card, and it effectively adds RAM. I made a lot of modifications to my script for the new raspbian version, one of them is installing ZRAM differently for the Pi. On the Ubuntu version, it is an installable package, but for Raspbian it is a downloaded and installed script.

2. The way I currently do the INDI and KStars build, it uses the absolute bleeding edge KStars and INDI. It doesn't have to be done that way. You could download the source of the latest release instead and build that. That could be an option I add to my script in the future.

3. I've been using SD cards for my PIs since 2016. I haven't had any issues or corruptions yet. And I've used them quite a lot. But you can probably do something else

4. I don't have a case yet. I've not been happy with what I have seen so far. Right now my Pi4 is used for experimentation. I currently am using my Raspberry Pi 3b's and 3b+ for imaging. So far I haven't seen it get above 80 degrees. I have some small heat sinks on the components to dissipate heat though.

• There is a zram-tools package for Raspbian, not sure if you are aware of that. Using that the zram setup might look pretty similar to what you are doing on Ubuntu.
• You could probably checkout to a particular tag when cloning the git repositories. Perhaps that's something that could be specified via command line or environment variables?