chlopak

Dear Waldemar, there is no need to change the hardware, actually the mount runs particularly well. I only faced the problems with autoslew 5.1.3.9 and I wanted to ensure, when upgrading to 5.2.4.0 every possible source of problem was taken into account. Yesterday I upgraded to 5.2.4.0 and evidently my mount has returned to the performance I'm used to. Regards, Ralph

Hi Robert, that was exactly my question: which parameter in which ini-file should I modify? But meanwhile I received an answer from ASA: Sehr geehrter Herr Wilhelm Wir sind vor einiger Zeit davon abgekommen die Encoder Auflösung separat zu setzen. Die Abweichungen sind nicht besonders groß, und werden durch das Pointingmodel perfekt korrigiert. Es sollte also mit der aktuellen Version, und den alten Encodern gut funktionieren. Mit besten Grüßen Wolfgang Promper Google translation: Dear Mr. Wilhelm We have some time ago decided to set the encoder resolution separately. The deviations are not particularly large, and are perfectly corrected by the pointing model. So it should work with the current version, and the old encoders work well. Best Regards Wolfgang Promper Well, if this is the case, it's ok for me. Regards, Ralph

Hi, I have a DDM60pro from 2010. In this version you had to determine the encoder resolution yourself before using it seriously. Does anybody know, whether this is still possible with the latest autoslew version, 5.2.4.0? Alternatively, how can I enter the encoder resolution I measured some years ago into the current version? Thanx for your support! Regards, Ralph

Hello, is it possible to have two different versions of Autoslew and Sequence, say 5.1.1.6 and 5.2.0.4, installed on the same computer, so you can switch between them ? This would be great in order to play with the beta version and work with official version... Regards, Ralph

Hi, can anyone explain me how to use the "Track on Comets" feature of autoslew in practise? How do I get the Delta Speed in RA and DE for comet ISON on let's say December 1st, 7 o'clock, just to have an example? Thanx in advance for your answers. Regards, Ralph

Ok, folks, here's the solution: you have to set the parameter Max. Magnitude in the plate solve settings down to 11. Why? Well, since sequence only reported an error with solving the plate but didn't tell which error I switched to the pinpoint GUI and tried to solve the plate there. Here I got a clear error message which said that there are too many stars (due to the wide field). So I reduced the max magnitude until the error message disappeared in pinpoint. But there was another challenge ahead of me.... When I switched back to sequence and changed the parameter there, I still got the error message. It took me another hour to find out that the changes only take effect after you save the settings ! Best regards, Ralph

Hi, yesterday I tried to use sequence with a very short focal length (80mm lens and KAF8300). Unfortunately sequence couldn't plate solve any image ! Maybe this is because I only adjusted the Plate Parameters Horiz Scale and Vert Scale? Do I have to adjust any other parameters? Who can help me ? Thanx, Ralph

Hi Bill, thanks for the information! This is now very interesting, both you and Bob actually shouldn't face any vignetting according to the statements and technical drawings from QSI. I wonder what is the reason for the vignetting both of you are reporting? Regards, Ralph

Hi Bob, thanx for your answer - which surprises me a little. Why do you crop? Can't you correct the vignetting with flats? Or are the corners really shadowed by the ASA adapter? According to the QSI homepage the camera shouldn't have problems with f/3.6. Regards, Ralph

Hi, is there anyone in the forum you uses a QSI 5xx/6xx and wsg body with his ASA Newton (N series)? Would you recommend this combination ? Regards, Ralph

Hi Pavel and Matts, thanks for your answers, sounds good so far. @Matts: I assume you are working with f/3.6, too. Have you compared lights with OIII 5nm and 3nm filters? Are differences in vignetting? Very nice pictures, btw ;-) Regards, Ralph

Hello, I have an ASA 10N and I want to go for narrow band imaging. Since my telescope works in a very light polluted area I want to take the filters as narrow as possible, e.g. Astrodon 3nm. However I know that filters can be too narrow, especially when playing together with fast optical systems like f/3.6 or even f/2.8. Which filters do you use and what are your experiences and recommendations ? Regards, Ralph

...continued: After you successfully executed the manual homefind procedure via the menu entry everything seems to work fine except for (again:) the homefind button in the main window: it believes that the motors are still switched off (although they are switched on now of course) and produces above described error message. You have to turn the motors off and on again in order to make the homefind button work again (however automatic homefind only...). Regards, Ralph

...and the answer is: It works as expected if you are using the Autoslew menu "Mount->Home Find". It doesn't work with the Homefind button . Regards, Ralph

Hi, I was just trying to execute the manual homing procedure as it is described here: http://www.astrooptik.com/asa/Autoslew5048_Homefind.pdf The description says: "Manual Homing Start Autoslew and don’t turn on the motors now. Instead, click the Homefind button. Now MANUALLY move your mount first in RA slowly to cross the reference mark. You will notice that once the mark is passed, there is a beep and the mount gets powered in this axis. ..." However, when I press the homefind button then I get an error message: "You can't Homefind because Motors are turned OFF. You can turn on Motors by clicking on 'Motor is OFF' button." What am I doing wrong? (I'm currently using Autoslew 5.1.1.6 with a DDM60pro produced 09/2010) Regards, Ralph