Jump to content

Banner.jpg.b83b14cd4142fe10848741bb2a14c66b.jpg

Mount stopped tracking - ASCOM issue?


Adam1234

Recommended Posts

Can anybody shed any light on what happened here?  Was imaging happily, was working fine all evening, guiding going well, half hour left on imaging plan before the rosette got too low, then all of a sudden I had this message pop up in PHD2 and guiding stopped:

 

1576180527_errorphd2.thumb.jpg.574f5ec8fb9b6d9f25d1760ca6afa1a1.jpg

 

I closed PHD2, tried to start guiding again and I noticed that the stars on the guide scope were trailing, so I thought that was weird. 

Went into APT and noticed tracking had stopped.

I tried turning tracking back on but then kept getting this message:

1911487743_errorapt.jpg.f5c00062bb237a9474ccb2d8015e28ec.jpg

 

No idea what caused this, but I disconnected the mount from APT and tracking then worked all seems OK now, but just curious as to what may have happened. 

Any ideas?

I thought it could have been the celestron power tank running low, but that's not it as I've just checked and it's still half full

Edited by Adam1234
Link to comment
Share on other sites

As the message said "check the debug log for more information"........... !

You'll need to upload the GuideLog and Debug Log to the PHD2 help site.

Details on how to are in the Help menu of PHD2

Make sure you upload the correct date files.

https://groups.google.com/forum/?fromgroups=#!forum/open-phd-guiding

Michael

 

Link to comment
Share on other sites

Thanks Michael, 

I checked the debug log, but I don't believe it was an issue with PHD2, rather more of a symptom - the error message in PHD2 it seems was a result of ASCOM disconnecting, hence why the tracking in APT disabled, as to why ascom disconnected no idea but at least I got it working again within minutes.  

23:43:12.358 00.003 5700 ASCOM Scope: DisPHD2_DebugLog_2021-02-27_184619.txtconnecting

PHD2_GuideLog_2021-02-27_184619.txt

PHD2_DebugLog_2021-02-27_184619.txt

Link to comment
Share on other sites

  • Adam1234 changed the title to Mount stopped tracking - ASCOM issue?

This happened again last night while imaging - I disconnected the mount and reconnected and it seemed to work fine after that. 

 

I have a theory after speaking to a work colleague who is also a computer scientist - I recently had an update to my laptop (Windows 10), so could it be likely that I need to install the latest ASCOM drivers?  

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • 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.