There is a new Raspberry Pi Camera Module 3 available with autofocus and a focus range 5cm to infinite. Should be able to do the job using the python Picamera2 library.
Read More...
Just to add my idea:
What I could imagine is a kind of simulation mode for the mount. Based on a start time (date/time) and the target's RA/Dec data, Ekos could calculate the target's trajectory during the night and move the mount as if it were tracking the target (of course without guiding or plate solving). To do this, the orbit data would then have to be converted into control impulses for the mount and the mount would follow the target at a selectable speed. Since the orbits of targets can be very different (e.g. circumpolar or non-circumpolar orbits), it is not possible to estimate how this affects the movement of the telescope with respect to the pier.
Kurt
Read More...
Hi Fred,
well, not exactly. I want to check if there is a chance that the telescope hits the pier some time AFTER the meridian transit. Such a hit is expected with a tripod (so with three legs). For (column) piers, reseller TS Optics claim that for piers like this one:
www.teleskop-express.de/de/montierungen-...wicht-nur-8-kg-13985
that it is "ideal for astrophotography because the telescopes do not hit the tripod legs, photography is possible until well after the meridian passes." (translation of their claim). So what is "well after meridian pass"? Can I trust that the mount can track the target until dawn? I am not sure...
Read More...
With kstars/Ekos, is it possible to run the mount during daylight to find out whether the telescope hits a pillar mount support after meridian transit when a certain target is being tracked, this at a higher speed then sidereal? If so, what settings do I have to make?
Read More...
Hi,
After nine weeks of cloudy nights, I was able to try the procedure you suggested today and it was successful. I wasn't aware that one should do that.
BTW: the link stellarmate.com/support/faq/mounts.html?view=faq&faqid=33 returns a 404 error.
So issue closed.
Thanks Hy
Read More...
Thank you Hy for your detailed analysis.
I will look at your suggestions and then report back here.
Unfortunately, the weather forecast for the next two weeks is unfavorable, so that I don't yet know when I'll be able to go into the garden with the telescope again.
Kurt
Read More...
Hy,
I also have a similar problem with meridian flips as Frank. I didn't use it during spring/summer, but since late summer I've had a heavier Newton telescope for which I wanted to use the original mount tripod. The meridian flip failed twice in September. I noticed that after the failed flip, the telescope did not return to the park position, but landed significantly away from the meridian.
I have since decided my imaging sessions, one before and a second after the meridian transit.
Since this procedure is time-consuming, I made several attempts last night to understand my problem:
1. PAA was successfully completed, then the telescope returned to the park position (time 19:33:28), RA: "02h 07m 54s" DE: "90° 00' 00"
2. I then approached several stars and then returned to the park position because the solver partially failed (time 19:49:25 (solver OK), 19:54:03 (solver failed), 19:58: 37 (solver OK), 20:29:01 (solver failed), 20:31:34 (solver failed)). The parking position was different in each case, but DEC was DE: "78° 26' 40". Shouldn't the telescope have returned to DEC 90° 00' 00''?
3. I did another PAA after that to correct the mount model. The overnight session with the scheduler after the transit was then successful. The session was canceled at 05:41:27 due to dusk.
4. This morning I manually put the telescope in the park position at 07:44:09, DE: " 90° 00' 00 (!!) , because after the scheduler was aborted, the park position was not approached and the focuser was not in the 0 position (can one do this with a script?).
I loaded the “failed-align-frames” and the log to www.dropbox.com/scl/fi/61fbrglby93reqgv1...fd2cm2viyn531kx&dl=0 . I never used dropbox so far, so if there is any issue with the link let me know.
Any information about my issue is welcome.
Thanks
Kurt
Read More...
I want to use the focuser driver "Waveshare Motor Hat" on my Mac (OS Ventura 13.5.1) under kstars. The author Kevin Ross asks to copy the associated XML file to the Mac into the associated directory. Where can I find this on the Mac? Ekos INDI Options says for the location 'INDI drivers XML Directory' the folder "internal INDI drivers". But where is it?
Do I need to reference the XML file somewhere else?
thanks
Kurt
Read More...
Hi all,
For astrphoto sessions I use the scheduler and very often shoot with multiple filters in one night. I usually do a re-focus between filter changes. I then observe that the first image with the new filter is blurred. Maybe I overlook something, but I haven't found any parameter that provides a pause after filter change/re-focus.
What do I have to do to avoid the first blurred shot?
Thanks
Kurt
Read More...
Thank you both for your reply. I want to use a nema 17 stepper motor with built-in 20:1 gear connected to the coarse focus knob.
Kurt
Read More...
Hi Kevin,
So far I have been using the waveshare motor head driver on a TS refractor and have adapted the NEMA 14 stepper motor to the 10:1 fine drive. This brings me with about 1240 steps in the area of a good focus before I start the autofocus.
I would now like to use a mirror telescope and can probably only connect the motor to the coarse drive, since the 1:10 fine drive has a very thin shaft (2.4mm) for which I have not found a suitable coupling. Is this combination suitable to achieve a good autofocus? In case not, is there eventually another possibility (different motor)?
Thanks
Kurt
Read More...
In the meantime I have spoken to Teleskop Service, where I bought my telescope. They admit that the telescope is probably not optimally corrected in the blue. I have now decided not to use a filter and to invest the money in a reflecting telescope that, in principle, does not exhibit this issue (if correctly collimated).
Read More...