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

1 Neutral

About richardejm

  • Rank

Profile Information

  • Interests
    Mesu mounts, Astrophotography, DIY mounts, DSO's , Galaxies, Cosmology
  • Location
  1. My 2p's worth: If a windows update reset your laptop then make sure that the windows update feature is set so that doesn't update until you say so. An imaging session of mine was foiled by this once. If you had a BSOD then check your laptop's memory is plugged in fully (if reachable). BSODS are usually faulty hardware or buggy drivers. Remove any unused software, especially if it uses a driver.
  2. Another suggestion (although more expensive at around $99 ~ £76) - sequence generator pro. This does almost everything you could want: sequences (obviously) finding targets using plate solving - works very well autofocus filter control mosaics auto-meridian flip with recentering afterwards It doesn't do image processing as maxim does It integrates with phd2 for guiding very well. see http://mainsequencesoftware.com/Products/SGPro demo version available for 30days Everyone has their favorite software and this is mine!
  3. The reason I think it is running slow or fast is that : stars show long trails at 1430mm focal length (C9.25+f6.3 reducer) when SGP was set to continually take 2 second images of vega (while focussing) I noticed that it kept moving from frame to frame. phd does RA corrections all in one direction I did a measurement of the amount of drift by doing this: got the PA accurate to within 1 arcmin (using sharpcap - very good software) clicked the "freeze declination" option in sitech's config pointed at a star and exposed for 5 mins measured the length of the star trail and converted the length in pixels to arcsecs worked out the new encoder ticks value, reconfigured it to go faster and took another picture to check......and.....it didn't work reconfigured to go slower and retested....nope! (I did of course take a copy of the original config file) So it looks as though I need to take advice from Lucas after all...Ho hum!
  4. The firewall should be ok since you can already connect. Yes - if you login as administrator then you should be ok. If not then you need to tell the objs pc that your user can accept remote connections.
  5. I think I know what might be the problem - both SiTech and phd are compensating for declination at the same time. I can turn off compensation in phd but of course, phd doesn't know what sitech is doing so it still thinks that the ra rate is odd. I can still calibrate and get it to guide ok-ish. Dan Grey is going to modify sitech for me so that compensation can be turned off. Phd should then be able to work correctly. I have noticed another problem (sigh) - all the ra corrections are in the same direction so probably means that the ra tracking rate is slightly off. Fortunately another SGL member (https...../247247-mesu-200-ra-guide-speed-correction/) had the same problem and succesfully adjusted the encoder settings to make it track at the correct rate. When the clouds part, I will try that.
  6. Nope - you are configuring the rdp server on the obs machine which will only allow in users that it knows about. When you connect, you enter the name and pw of a user on the objs computer. Windows on the objs machine then authenticates it - because it knows its own users but not anyone elses. If it recognises the incoming user as one of its own and that user is allowed to connect then it works. If you think about it, that's the way it has to be otherwise any tom dick and harry could connect from anywhere!
  7. Hi, if both your pc's are connected to the same router then you don't have connectivity problems. This is how my study and obs pc's work. Since you say that it is rejecting your credentials then rdp must have connected. Have you set the obs pc to allow remote desktop connections? Goto settings/remote desktop and select "enable remote desktop" = on (on the obs pc) Click on "select users that can remotely access this pc" Enter the name of the objs computer user that you want to allow. Usually that is the one you normally log in with. Administrators are always allowed. Non-admins have to be given permission. that should do it. Make sure you connect to the objs computer with this user. regards
  8. Thanks everybody for your help! I will try these suggestions the next clear night (if that ever happens).
  9. Thanks for the tip. I did wonder if the RA rate varied with the declination, I believe it varies with the cosine of the dec angle but Arcturus is at dec 19 degrees so the factor would be 0.94 which is not enough to explain the problem. However, I will try your suggestions if the clouds ever go away!
  10. Hello! I am installing and configuring my nice new mesu mount (with SiTech controller) but have come across a strange problem that I hope someone here has seen before or can help me with. I was attempting to get PHD to calibrate but it always failed saying that it could not move RA enough to complete the job. I ran PHD's star-cross test on Arcturus and got a cross in which the RA arms of the cross are almost exactly half that of DEC (see attached). What is odd is that the guide rate in both axis is the same (5 "/s) and the encoder ticks/rev are about the same: SiTech's config file says: AlMotTicksPerRev=7952383 AlScpTicksPerRev=10000 AzScpTicksPerRev=10000 AzMotTicksPerRev=7961372 (same in the controller config) Has anyone seen this before ? More importantly, does anyone know how to fix it?
  • Create New...

Important Information

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