Atik Cameras Forum

General => Equipment => Topic started by: yzhzhang on April 10, 2015, 01:17:54 am

Title: ASCOM Atik Driver Not Stable
Post by: yzhzhang on April 10, 2015, 01:17:54 am
Hi All,

This is my first post here. I'm a user of Atik One 6.0 combo and I use it together with Paramount MyT mount and The Sky X (TSX). My computer system is Win7 64 bit. I notice that the ASCOM driver is very unstable under TSX, especially when I try to connect the GP guider camera. After click "connect" in the autoguider tab it just froze the TSX, and I have to end the program in task manager. I just re-download the Atik core installer and re-install all the drivers so they should be up to date. Does anyone experience the same or does anyone has a solution?

Thanks,
Yizhou
Title: Re: ASCOM Atik Driver Not Stable
Post by: Chris on April 12, 2015, 09:18:30 am
There's no evidence that the ASCOM driver is unstable.

Try enabling logging in the ASCOM driver (instructions to do this are in the driver help file) replicate the problem and post the log files.  If you can also get log files from TSX that will be a great help because I can then compare what the driver does with what TSX does.

Try with a different acquisition program, Nebulosity, Sequence Generator Pro and/or PHD2. Get some confidence that things work.

Try contacting Atik support directly.  I'm not sure how much they monitor this site and I've not seen much from them here recently.  Give them FULL details of what you have, what you are trying to do and what happens.  Describe what happens, not what you think the problem is, that's their job.

It's not a good idea to keep uninstalling and reinstalling the same software.

There is nothing that can be done without evidence in the form of driver logs at least.

Chris
Title: Re: ASCOM Atik Driver Not Stable
Post by: NickK on April 20, 2015, 09:17:07 am
With TheSkyX there are two pieces of software:

1. Software Bisque's TheSkyX ASCOM Plugin that connects TSX to ASCOM
2. ASCOM ATIK Driver that connects ASCOM to the camera

So it may also be worth setting up the logs for TheSkyX (under preferences) then passing these logs to Software Bisque too - incase it's the ASCOM plugin causing issues.
Title: Re: ASCOM Atik Driver Not Stable
Post by: -Amenophis- on July 28, 2015, 07:36:33 pm
It's a same for me....

Do you have a solution?
Have you identified the problem?

Thank you
Title: Re: ASCOM Atik Driver Not Stable
Post by: Chris on July 28, 2015, 11:34:09 pm
There is no evidence of a problem with the ASCOM driver.  I asked the OP and got nothing.

Nothing can be done without some sort of evidence that there is a problem.

Chris



Title: Re: ASCOM Atik Driver Not Stable
Post by: -Amenophis- on July 29, 2015, 08:14:46 am
 :'(
We are left to ourselves !
Title: Re: ASCOM Atik Driver Not Stable
Post by: Chris on July 29, 2015, 08:34:47 am
While people don't provide any information then there's nothing that can be done.

My first post in this thread describes the sort of thing that we need.

Chris
Title: Re: ASCOM Atik Driver Not Stable
Post by: Richard Smith on November 18, 2015, 07:26:31 pm
I am also having great instability with the ASCOM Atik driver and TSX.  I am using an ATIK One 6.0 with TSX running on a dedicated Intel Celeron NUC device running Windows 10.  The ASCOM driver will appear to work just fine, except it will just quit in the middle of taking a long exposure.  I get an error that the Atik ASCOM Server has stopped working.  Most recently, an instability occurs where trying to start an image capture results in a TSX error stating that a filter wheel move command is already in progress (a command that I did not initiate), which locks out the image capture and hangs the camera.  Using the ATIK Universal driver is more stable, except that it crashes TSX every time I try to disconnect the camera.

Hoping someone already knows the answer, but I will post some trace files later tonight.

Update:  I went back through my ASCOM camera trace files to find the files that show what happened when the Atik ASCOM Server stopped working.  Unfortunately, it doesn't appear that those trace files get saved when the server quits.  Am I doing something wrong?

Thanks,

Rich