Jump to content



  • Posts

  • Joined

  • Last visited

Everything posted by kens

  1. You mean like this https://www.avalon-instruments.com/products-menu/mounts/m-zero-obs-wi-fi-detail
  2. It looks like PHD2 is receiving commands intended for INDI server. PHD2 should be on port 4400. Ekos profile should look something like this
  3. If you look at the Stellarium screen shot from the time of the equinox in 2000 you can see that NGC7822 is close to the same hour angle as the Sun and which is by definition RA 0h0m in J2000. It is the position of the sun at that exact date and time that defines RA 0h0m for J2000. And that is low in the SouthEast. At that date/time the meridian is at an RA of about 19h18m. So why would you expect an object near RA 0h0m to appear near the meridian? If you advance the Stellarium clock to midday of the same day the sun appears overhead as does NGC7822. The Sun is no longer exactly at 0h0m but still quite close at 0h0m40s or so. The RA of NGC7822 does not change. It seems you are confusing two different approaches to RA and appear to have redefined RA: At the exact time of the equinox the sun is at RA 0h0m. No meridian or midday involved in this definition. When the sun is at the meridian its RA is the same as the sidereal time. Applies on any day at all. Not related to the equinox. Also, sidereal time is not the same as terrestrial time. Does that help?
  4. From Wikipaedia: https://en.wikipedia.org/wiki/Right_ascension So it is measured from the position of the Sun at that date/time
  5. Moving the tripod would almost certainly destroy your polar alignment.
  6. It looks like the mount is not responding to dec guide commands in either direction until its a big correction. Then it overshoots. That would be a mechanical issue, most likely. You've got a lot of huge spikes, especially in RA that look like the scope is being bumped. Did you lose many subs?
  7. Once you've changed guide rate in EQMOD it should stay that way for future sessions. Going on memory, I think PHD2 only reads the guide rate when you create the profile with the wizard. After that you would have to change it manually, in the advanced settings calculator, to the value in EQMOD One of the many reasons for creating a new profile with the wizard. PHD2 is constantly being imprved so a lot of what is on the internet is out of date. The best place for information is the official web site and support forum.
  8. The guide log includes the calibration and also what equipment you are using. Based on experience I'm guessing you are using the EQMOD driver which has the quirk of defaulting to a guide rate of 0.1x sidereal since that is what I see on the screen shot. That guide rate is way too low. The guide log would confirm that you are using the EQMOD driver in which case the instructions I linked are relevant. If some other sort of mount then you still need to increase the guide rate but the linked instructions would not help you. The log also contains the raw data for the calibration which does not necessarily graph the same as shown on the screen shot. The raw data helps with the diagnosis. In any case, adjust your guide rate to between 0.5x to 0.9x then try another calibration. If you use the profile wizard and enter the correct values it will calculate the right calibration step size for you.
  9. PHD2 only knows about guiding. I don't use APT so can't comment on that but in general software only knows what the mount tells it. Aside from setting circles (which are generally not very accurate) there is plate solving where you take a photo and the plate solving software works out from that where you are pointing. In your setup, once you know where you are pointing adn where your target is you can use the hand controller to move to the target. There is some calcuation involved to work out how long you need to press the buttons for. But you can plate solve progressively till you get onto the target. A very manual way is to use a planetarium (e.g CdC or Stellarium) and your finder scope to star hop from one prominent star to another till you get to your target.
  10. I can only make specualtive guesses without the guide log but start here to set a more appropriate guide rate. I assume you have EQMOD. I'd suggest you start over with a new profile using the profile wizard. https://github.com/OpenPHDGuiding/phd2/wiki/EQASCOM-Settings Then read the best practices: https://openphdguiding.org/phd2-best-practices/ And always provide a guide log when you need help: https://openphdguiding.org/getting-help/
  11. @stevepsheehanCan you attach the guide log? The Help menu is the place to look for them
  12. Looks that way. Normally that is the case and the GPUSB would plug into the mount guiding port. In this case it looks like the handset has been modified to achieve the same outcome. Cartes du Ciel wont work with your mount. It needs a Goto mount to show where the mount is pointing and to move it around. If you want to know where the mount is pointing you would need to plate solve. To move the mount you need to do it by hand or via the handset. With the handset the highest speed is 16x sidereal which would take over 20 minutes to slew 90 degrees.
  13. Your seconds GA run is a mess and totally unreliable. It looks like your mount got bumped or something slipped as it moved around 80 arcseconds on two or three occasions. Maybe the Alt/Az bolts were loose? Due to your bad initial PA you should recalibrate once your PA has completed. A bad PA affect the accuracy of calibration. Do the recalibration before you run the Guiding Assistant. To recalibrate, hold down the shift key while clicking the Guide button
  14. I'm not sure what this device is. Based on the label I suspect it is an ethernet crossover which is generally unnecessary these days. Just because the plugs are the same does not mean they are electrically/electronically compatible. I'd caution against trying that. You can connect the camera directly to the PC but for it to be usable by PHD2 you need an ASCOM driver for it or hope that the built in drivers in PHD2 can talk to it. Check with the supplier before buying. The GPUSB converts USB signals to ST4 signals, just like a ST4 camera would. ST4 signals simulate pressing the button on a hand controller. There are separate wires for N/S/E/W. N/S = Dec and E/W = RA. So the mod to you handset has connected the ST4 wires to the outputs of the button on your handset which then controls the mount.
  15. You need to attach a guide log for any analysis. The screen shots have too little information to give any sensible guidance
  16. You'll also need to install PHD2 to do your autoguiding: https://openphdguiding.org/ You'll need to choose GPUSB as your mount in PHD2 then you will be able to guide. But your mount cannot report its position so CdC and similar tools cannot show where it is. You need a goto mount for that. Check that there is an ASCOM driver for your camera. I had a quick look and found no mention of one. You'll need that to connect it to PHD2. Or get a caera that has an ASCOM driver or is PHD2 compatible. It is remotely possible that the WDM driver in PHD2 will recognise it. For navigating the sky you either need to learn how to star hop or learn about plate solving. You might want to get the basics going first
  17. And the winner of "Bodge of the week" is.....
  18. Probably better to sart a new thread. The title of this one is PHD2.6.2 which is years old now so would not get much attention Have a look here first: https://openphdguiding.org/getting-help/ The PHD2 support forum is best suited to these sorts of problems as it often requires poring over the debug logs which is not a task for the lay person. Once you have the camera working then have a read of: https://openphdguiding.org/phd2-best-practices/
  19. You need some way of connecting the computer to your mount for autoguiding to work. The two most common ways are: connect the camera to computer via USB and connect camera to mount with ST4 connect camera to computer via USB and connect mount to computer via another USB Method 2 is preferred because it allows more functionality but is not an option for you. As far as I know you would have to modify your hand controller to provide an ST4 connection for option 1. Now even if you could get that part working you need to be able to send commands from your computer to the mount. For that you need a device like an AstroEQ which plugs into a USB port and converts to ST4. I think you'd be better off getting a camera with an ST4 port and/or a mount with at least ST4 connection. Unless you are into DIY electronics and programming.
  20. It is indeed in the first link along with screen shots showing how to do it. And from inspection of the guide log that is the first issue to resolve..
  21. Start with this: https://github.com/OpenPHDGuiding/phd2/wiki/EQASCOM-Settings Then have a read of: https://openphdguiding.org/phd2-best-practices/ If you still have problems: https://openphdguiding.org/getting-help/ or if you prefer you can upload your logs to the forum.
  22. +1 I leave the wifi permanently as a hotspot and if I want to check on things I just plug in an ethernet cable . That also means it only gets updates when it is on the ethernet because that is its only route to the internet. The less you change the setup the less chance of things going wrong
  23. One second is a lot when guiding. You would normally take exposures of 2 to 3 seconds then guide with corrections in the order of 100ms at 1x sidereal (that would be 1.5 arcseconds). So with 1 second backlash you are moving the motor 15 arcseconds before the mount moves and if it is inconsistent you could end up moving the scope a large amount if you add that to your guiding pulses to try to compensate. On top of that you delay the enxt exposure by 1 second which is a significant amount for the normal 2 second expsoure. During that time any drift is moving the guide star 30% further than usual. The gear you are looking at is not the only contact point. There is also the worm to ring gear interface which is under the housing. There should be screws on the housing to adjust that gear mesh. Backlash is less of an issue in RA. The RA axis is always moving West at a constant 1x sidereal. To guide east is just stops till the stars catch up and to guide west it needs to move at 2x sidereal. The gears should not unmesh except when slewing East at more than sidereal rate.
  24. I doubt you'll ever get to a single point . At some point you will reduce the PA error enough that ther will belittle drift in Dec but then you will get RA trailing from periodic error. Guiding is the way to correct for that. If the mount isn't responding my first guess would be backlash. Any time you reverse direction you will experience it. With guiding there are ways to mitigate the worst effects. The simplest it to make dec guiding corrections in one direction only - opposite to the drift caused by PA error.
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. By using this site, you agree to our Terms of Use.