Jump to content

stephankueppers

Members
  • Posts

    13
  • Joined

  • Last visited

Recent Profile Visitors

50 profile views

stephankueppers's Achievements

Member

Member (1/1)

  1. Hi Robert! That is correct! But if i copy the last XP Autoslew.ini file - with the wrong folder-pointer - to the Win10 program-folder of Autoslew, the fault starts. Stephan
  2. Hello Robert, hello Mark! I think I found the real problem, i.e. the lack of accuracy of the mount !!! One should be able to read! When opening Autoslew, the log file says that Autoslew cannot find the config file. When I noticed this, I took a closer look at the Autolslew.ini file. The folder for loading the configuration file is specified in this file under [More Parameters]: "Last Pointing-Configuration File = C: \ Documents and Settings \ All Users \ Application Data \ ASA \ Autoslew \ 20120525a.cfg". Since I had a Windows XP system up to now, this was fine too. But my new PC has a Windows 10 system on which this folder does not exist. Windows 10 stores such files under c: \ ProgramData \ ASA \ Autoslew. After creating a new configuration under Windows 10, Autoslew tries to save this configuration file under c: \ Programme \ Autoslew. However, this cannot work because this folder does not exist either. Correct would be under Windows 10 c: \ programme(x86)\ Autoslew. For this reason, no new configuration file is created and Autoslew continues to point to a wrong or a nonexistent folder. Of course, that can't work. The output error is the wrong - and by the way the only one - folder specification in the Autoslew.ini. Who pays attention to this! I will change this folder accordingly and, if Heaven permits, try it out. Kind regards Stephan
  3. Hello Robert! I bought the DDM60 at 20.07.2010. Therefore i think it is one of the first Mounts, where i had to find out the encoders settings. Before i made the new setup at the new windows10-pc, i asked the ASA-support what to do and Mr.Promper gave me the advise to copy the autoslew.ini and the cl-servos.ini to the program-folder of autoslew. Therefore the old and new settings of cl-servos.ini are equal. For the axis 1 the setting are 15244 and for axis 2 the setting are 12566. I will make a new try, as soon as the weather give me a clear sky. Best regards Stephan
  4. My mount is a DDM60 with incremental encoders. Stephan
  5. Hi Robert! My Mount is a ddm60 with Thank you for your idea, I will try that. For my new camera with very expansive pictures (120mb/picture) i had to make a new setup with a new windows10-pc. By doing this, i thought to install the newest Autoslew (5248) and the newest Sequence (0211). That might be the problem?! I will go back to the older Autoslew Version 5111 and the last working configuration, which was stable to my mount, and try it again. Ich werde auf die ältere Autoslew-Version 5111 und die letzte funktionierende Konfiguration zurückgreifen, die zu meinem Mount stabil war, und es erneut versuchen. If i am sucessful, i will update to Autoslew 5248. Hope this works! Best regards Stephan
  6. Hello Robert! Thanks for your reply! My location is Juechen,Germany,NRW, a little town near Moenchengladbach/Neuss. You are right! Visual-Pinpoint use the spiral-search. The average-pointing-error are ca.15 arc-min. The way, you described, are similar to my actions. First i made a good polar-aligment (ra 0,3', dec1,0'). Then i determine the ERF (5-stars, 1-2-1-3-1). At last i synch a star near meridian an try a greater autopoint (18 stars, east and west). exactly the solving of this 18 autopoint-pictures are the problem! If i can solve this pictures first with Pinpoint and then make a PointingError.pox-file with Sequence, it will be a good work around and will not be very time-consuming (10min). Best regards, Stephan
  7. By the way: why can i not select and use the 5x5 spiral search in sequence?
  8. In Visual PinPoint i use this settings: Min Sigma 3, Filter FWHM 8, Hor./Vert.-Scale 0,558, Max Mag 15, Exp 40% 5x5 Spiral search, Max match residual 8, Min Stars 15, Max-# stars to match 200 and Max-time 120s. Catalog USNO A2.0. Pinpoint solves every picture.
  9. I use a telescope with 2788mm/250mm. My camera is a QHY600PH (pix-size 3,76 x 3,76 Mikrometer² mit 9 576 x 6.388 pixel full-format). My pointing-pics are made with 5sec with 2xbinning and luminanz-filter. The settings of sequence are Min size 9.00, Min sigma 3.00, FWHM 8.00, Min stars 15, Maxmag 15, Timelimit 120s. I use the gsc-and the UsnoA2.0-catalog. Sequence solve 2 two of 18 pictures with this settings. With the standard-settings sequence solved 0 pictures. I tried calibrated and uncalibrated pictures and expose-time 5s, 15s and 30s. Nothing worked.
  10. Hi Mark! Thanks for your answer! I have some problems to solve my pointingfile-pictures with sequence. Therefore i first would like to solve my pictures direktly with visual-pinpoint and than second build the pointingerror.pox-file with the solved pictures in Sequence. Stephan
  11. Can someone tell me more about the structure of the PointingError.pox-file? Can i first solve the point.pics with Visual-Pinpoint and then make the Autopoint-file? I didn't find anything about this questions. Thanks for help! Stephan
  12. Hi Mark! Thank you for your explanation. if you are right, that sequence interprets the number of steps as 1mm/1000steps, then i have 2,16mm/1000steps. I will try that! clear skies Stephan
  13. Hallo! I just try to use the sequence 0.2.1.1 with my TCF-S-focuser. I have questions about the focuser-settings. I don't understand the meaning of Focuser-Tolerance (TCF-s knows only Steps - one step is 2.16/10³mm with a range from 0 to 7000 Steps equal to 15,113 mm and step-rate from 200 steps/sec). The backslash are 15 steps (0,0324mm). Which setting should i use. Which setting should i use for Focuser-Timeout, Start Delay and Slew Settle Time ? Please help Stephan
×
×
  • Create New...