Hi Simon, I tried it out and found it quite challenging to get the balance of gain & exposure correct (using ASICap) to show the details. Its either too dim or too bright
I need to find more time to do this more leisurely.

Read More...

None = no guilding
Mount = guilding images are sent from the guide camera to the computer running the Guide module / PHD2. Guide / PHD2 works out pulses to move the mount to keep the guide star(s) in the correct position and sends from the computer directly to the mount. So there needs to be a connection from the computer running guiding to the mount. This is usually called pulse guiding.
Camera = guilding images are sent from the guide camera to the computer running the Guide module / PHD2. Guide / PHD2 works out pulses to move the mount to keep the guide star(s) in the correct position and sends from the computer back to the guide camera. The Guide camera sends the pulses to the mount so there needs to be a connection from the Guide camera to the mount. This is called ST4 guiding.

ST4 was the original way to do guiding. Pulse guiding is now the usual way as it involves 1 less connection (guide cam to mount) and 1 less hop for the guide pulses to have to make.

Read More...

Hi Keith,

There are a number of reasons why you might get this error. For me to be more helpful you'd need to post of the log with verbose Focus logging set on. But here are some thoughts in the interim...

You imply sometimes Focus was working, sometimes there were issues so seems to be an intermittent problem. You also mention you could make out stars in the frames where Focus was saying no stars were detected. This would fit with some sub-optimal parameter settings that work some of the time but not always.

You could post screenshots of the parameter settings and I could comment on those. Alternatively, you could run FocusAdvisor and let it update your parameters. Usually FocusAdvisor will pick a reasonable set of parameters for most systems that will minimise the sort of problem you have.

Read More...

How do I get a more "stable" version for Ubuntu 24.04 as there is not yet a nightly build for this platform available?
Or how can I install a previous INDI version? V2.0.6 or 2.0.5?

Read More...

That was my first guess Steve, yes.

ZWO (bit more generically all dedicated cameras) do nor use serial ports for communication but rather their own SDK and some libusb magic to find them.

Read More...

Several times last night I got a "No Stars Detected" warning and the AutoFocus failed even though there were clearly (though out of focus) stars in the frame. Stopped and restarted kstars and ekos a couple times, no help. This error basically stopped the Scheduler dead in its tracks. . .

Read More...

Verdict: loose/flaky cable.

I tried a test this morning, and the camera did not even show up in lsusb.

I apologize for my lack of knowledge. How do I reset indi server for Player one? I'm going to run the script. Thank you very much.

Read More...

Honnestly, I don't know for sure. What is certain, is that the mount did hang during capture, two times : the night before and the night when I took the screenshot.
Both times I was not able to understand the reason. I first thought of problem with meridian flip, but none of the targets would have needed this.
I'm facing some issues which I'm unable to determine whether it is because of my misunderstanding or they are real.
I tried to reproduce one that happened twice, last night and three nights ago, but unfortunately, there, in my living room, all worked correctly.
I'll open a ticket when it happens next time.
When I go on the field, I hope all will go smoothly. But next time I'll capture the session and activate all logs.

Read More...

Re-run setup.sh and re-define the indiserver with indi_playerone_ccd . There is also a dedicated script to perform this action: ./misc/change_camera.sh I would suggest rebooting once done.

Read More...

Does this have any effect on mount operation?

Read More...

Mattia; did not try unplugging and plugging back in, will do that today. As for the lsusb output suffice it to say that the output included an entry for the camera. I will also try removing the dongle for GPS to see if that changes anything.

Read More...

I will try it out this evening. If your application can support ASCOM, INDI then that should be able to support most of the popular cameras.

Read More...

That link is bit outdated. It just that libraries and compiler is now too old to be able to compile latest KStars. So upgrade to 22.04 or wait a bit and upgrade stright to 24.04 that should be released in a week or so.

Read More...

Can you expand on that? The link says Ubuntu 18.04 and higher is supported. Are you talking about Kstars? INDI? What Ubuntu versions *are* supported?

Read More...

The date correspond to this old issue: github.com/indilib/indi/issues/1719
It was quickly fixed and is probably present only in INDI version 1.9.7

Read More...

when you say nothing in dmesg, have you tried to pull the cable off and reconnect to see if anything happens on the usb bus? can you also post the output of lsusb?

Read More...

Yes I think that's the best option. If your ZWO act as standard usb camera, you can activate it's video stream directly from CC application, see version 3.2.0-beta3 here github.com/sajmons/CollimationCircles/releases.
If your camera supports absolute focus, you can control that too from CC (see camera controls button for that). With that you get hassle free colimmation of secondary and primary mirror. All you have to do is to change your camera focus distance from within CC app.

I'm not quite sure if this is working in latest version, but I'm working on it and will be available in final 3.2.0 version.


Read More...

Good point. So I think the most practical solution is use the wide-eye lens thats bundled with cameras such as the ZWO ASI224 or ASI120

Read More...

The version I have installed is 4.0.0 and the latest version from github is 4.4.0 since about 2 months ago.

Br,
/Markku

Read More...