Jump to content

Stargazers Lounge Uses Cookies

Like most websites, SGL uses cookies in order to deliver a secure, personalised service, to provide social media functions and to analyse our traffic. Continued use of SGL indicates your acceptance of our cookie policy.



  • Content Count

  • Joined

  • Last visited

Community Reputation

306 Excellent


About kens

  • Rank
    Proto Star

Profile Information

  • Gender
  • Interests
    Deep sky, fly fishing, cycling
  • Location
    Melbourne, Australia
  1. @gregk01I just did an experiment that might help you. I started up PHD2 and connected to the StarGo driver without any USB connection to the mount. The StarGo driver popped up a window asking for the COM port so I clicked OK. It was happy with this even though the selected COM port did not even exist. The connection went ahead as though everything was OK and the guide log shows pretty much the same as yours. So make sure that (a) Your USB cable is correctly connected to the mount and (b) that you have selected the correct COM port
  2. The data is showing RA Guide speed =0; Dec guide speed =0; RA=0; Dec=0, PierSide =Unknown. The non-reporting of RA and Dec suggests something more fundamental. With the Avalon mounts you need to set up the StarGo application by loading up a configuration file for the type of mount being used or it just wont work. Seeing as it is a new mount for the OP it is possible that this step has been omitted.
  3. The mount is not reporting any information via ASCOM. I'd suspect an issue with the setup of the Stargo application. e.g. It may be configured for the wrong type of mount.
  4. If you could attach your guide log that would be helpful
  5. If the orientation of your guide camera does not change and your mount can report declination to PHD2 and you got a good calibration near the equator then reusing the calibration should be fine. You only need to recalibrate near your target with ST4 guiding. If you are worried about your guiding, attach your guide log and ask either here or at the PHD2 support forum https://groups.google.com/forum/#!forum/open-phd-guiding
  6. I usually disbale Star Mass detection: https://openphdguiding.org/man-dev/Advanced_settings.htm#Guiding_Tab Or it could be a camera or USB problem? PHD2 has an option to save lost star images as well. It is normally enabled to some level so you may be able to view/post one or more of those. Not related but your guide rate is very low at 0.1x sidereal. You should increase it to 0.5 to 0.9
  7. Is it possible to use an astro camera (i.e. no lens) with the eyepiece style of grating? I'm thinking along the lines of an eyepiece projection tube to hold the grating with the camera on the end of the tube.
  8. I've been dealing with a similar issue. I had my ASI1600MM-C and AS1120MM-S plugged into a powered USB3 hub (so not using the ASI1600 USB) and that plugged into an Aaeon UP Core computer. All powered from the same 12V source. A lot of the time the ASI1600 would not get connected so I would have to unplug the USB cable and replug it. Never had a problem connecting to the ASI120. At first I thought I would need to delay sending power to the ASI1600 till after the computer had booted but that didn't help. So I'm now trying with a delay in sending powerto the computer so it boots after power has been applied to all the other devices. So far this has been working reliably for a few days. I suspect the issue may be due to the powered USB3 hub needing some time to register the ASI1600 before the computer boots and searches for attached USB devices.
  9. Please attach the log file rather than a screen shot.
  10. Make sure you aren't guiding on a hot pixel. Your guiding RMS is less than 0.1 pixels which is suspicious
  11. There is nothing magical or optimal about unity gain. It is just a value of amplification that causes one ADU to rcorrespond to one electron captured by the sensor. The charge on the sensor is converted to a voltage which is then amplified before being converted to a digital value in the ADC. Collectively, the errors introduced are quantified as read noise. If you are aiming for maximum dynamic range then try zero gain. But if you find that for a given integration time you have only a small number of subs then quantization error could be manifested in the result. If so the using a higher gain and more subs may be beneficial - but at the expense of saturation of brighter parts of the image.
  12. Its more the case that CMOS sensors generally have lower read noise so shorter subs are possible. You want the subs to be long enough on any sensor type, that the shot noise dominates the read noise. That way, stacking more shorter subs approaches the efficiency of longer subs in terms of getting a given SNR versus integration time. The length of the subs needed for shot noise to dominate read noise depends on gain and sky background. You want to expose so that the sky background equates to somewhere in the order of 3 to 10 times the read noise squared. When you can control the gain, lower gain gives more dynamic range but higher read noise. Once you get beyond 10 x read-noise squared you are getting more saturation with little gain in stacking efficiency. Below 3xRN squared you need more integration time to get SNR equivalent to longer subs. For the ASI1600, the optimal minimum gain is around 76. If your sub lengths at that gain are workable then use that. For NB you may need a higher gain to get workable sub lengths but with higher gain you lose dynamic range. A maximum gain of 200 gives a reasonable dynamic range - 10.5 stops; which gives some room for stretching. If you want something in between then unity (139) is a good choice. You don't need gain to be more precise than those three values and you don't need to be too precise with the actual values. I tend to use 70, 140 and 200 as they are easy to remember. Another factor with the ASI1600 is that it has a 12bit ADC so quantization noise is a consideration, especially at low gain. That can be overcome with more subs - say 40 or more. You are talking 50 to 100 subs so that is not really an issue for you.
  13. In that last log PHD2 was communicating with the mount. But it looks like you were trying to calibrate at the pole (declination 90). You need to calibrate near dec 0 to see any movement in RA.
  14. According to the log you were trying to calibrate at the celestial pole (Dec 90). Try calibrating closer to the celestial equator (Dec 0). Near the pole, any movement in RA makes only a small movement on the camera. Also, alter your step size back to 1000ms (or use the calculator) to give around 12 steps.
  15. You've attached the Debug Log by mistake. Please attach the Guide Log and we should be able to help ypou.
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.