Atik 11000 random lockups

[jarbi]

Hi,

My latest imaging sessions turned out to be a nightmare for unknown reason, here is what happened. I connected my Atik 11000 and then EFW2 filterwheel as usual to a powered USB hub and started my imaging session in Sgpro. After 2 frames the download of the next frame took forever, so I tried to stop the sequence - no chance, I had to kill it with Task manger. By restarting Sgpro the camera and filterwheel was not connecting anymore. Powered on and off both - now it was working again for some time, than the same lockup happened again. After 4-5 times repeating this annoying game the camera decided to work and I could do some imaging but lost more than an hour...

The question is: what happened here and how can I solve it ? The same setup worked already countless times without a hick. I’m using a Windows 10 Pc with the latest Sgpro and Atik drivers. Looking in the Sgpro logs I only find the fact that the camera was disconnected. If anyone had similar experiences please give me a hint,

Clear skies,

Janos

 

[Dr_Ju_ju]

Check power & USB leads especially if they 'move' (a little may cause a disconnect) which version of SGPro? as some of the betas' have issues...

as your on Win 10 make sure that the USB ports are configured to NOT go into standby (in device manager)

[jarbi]

5 minutes ago, Dr_Ju_ju said:

Check power & USB leads especially if they 'move' (a little may cause a disconnect) which version of SGPro? as some of the betas' have issues...

as your on Win 10 make sure that the USB ports are configured to NOT go into standby (in device manager)

Thanks Dr_Ju_ju, I am using Sgpro 3.0.3.169, this is the latest stable version. The loose USB port cannot be the reason, because an Asi 294 was running without interruption on the same USB hub the whole time. My fear that Window update did some "magic" somewhere which specifically affects the Atik software... The other day I have tested the issue with a previous version of the Atik and filterwheel driver- it made it even worse. I mailed Atik support as wel, but they are closed for business until the 3rd of September.

Cheers,

Janos

[Dr_Ju_ju]

If you've had a recent windows update then definitely check that all the USB power-saving\sleep settings are disabled....

[jarbi]

2 minutes ago, Dr_Ju_ju said:

If you've had a recent windows update then definitely check that all the USB power-saving\sleep settings are disabled....

Ok, I will check it this evening.

[whipdry]

As SGPro indicated the camera lost connection you might want to make sure that the power supply to the camera is stable, also think about replacing the USB cable from the camera to the hub. 

Picture below is a make do fix on a flaky USB, a couple of blobs of bluetack did the trick on this occasion... works OK on my permanent setup!

 

[jarbi]

Thanks for your helpful advises, I checked and indeed the USB power saving option was enabled. I have set it off now everywhere, so let’s hope it solves the lockup’s. For a test I must wait for the next clear evening 😉

Cheers,

Janos

Edited August 28, 2019 by jarbi

[Starflyer]

If this doesn't solve your issues try updating the Atik drivers.  I had this with my 460EX / EFW2 about a year ago after a Windows update and the latest drivers fixed it.

[old_eyes]

Useful to know. I never checked this, and sure enough USB ports were set to power save. I don't know if it has affected my setup, but I certainly have had some weird intermittent problems. But then doesn't everyone? 😉

[ollypenrice]

Where do we check for this disabling of power save?

Olly

[sloz1664]

Hi Ollly

Device manager> universal serial bus controllers> double click on each usb description (including hubs) Click power management tabs and "untick"  allow this computer to turn off power.

I'd go through the full list of usb devices, just in case.

Steve

[Dr_Ju_ju]

Also under Control Panel \ Power Options \ Advanced Settings \ USB settings :  USB selective suspend setting - set to disabled.

[Tom OD]

Hi All and especially Janos.

I m having or was and are now again having similar issues.

Using my Atik 11000 and SGP, the Cameras cooling would go from the -20/-20 display for Set point v Current reading would drop to 0/0 and any download would go on indefinitely. This would happen every 40-60 mins approx.

Olly had replaced the USB cable for me and it seemed to work for a while, then it happened again 2 nights ago. And in what seems like the reason I had to get Olly to power up my PC as it was down.

It only seems to go down if the power is off from the site / UPS for 8hrs plus, or if there was a Windows update. Time for me to check the USB in the device manager.

Thanks for the tip Julian and Steve. Blank blank Windows....

Tom.

 

[Tom OD]

On 31/08/2019 at 16:40, Dr_Ju_ju said:

Also under Control Panel \ Power Options \ Advanced Settings \ USB settings :  USB selective suspend setting - set to disabled.

Yes mine were set to Enabled. I'll be watching for the next Windows update to see if it resets it. I got there by a little different menu so here is what I had if anyone wants to see.

Tom

 

Edited September 5, 2019 by Tom OD
forgot to add pic

[tomato]

Blimey, that must be annoying, apologies if this has been discussed elsewhere, but can this element of Win 10 updates be blocked permanently somehow? 

[Tom OD]

On 28/08/2019 at 10:39, jarbi said:

Thanks for your helpful advises, I checked and indeed the USB power saving option was enabled. I have set it off now everywhere, so let’s hope it solves the lockup’s. For a test I must wait for the next clear evening 😉

Cheers,

Janos

Did it work for you? I hope to find out later tonight.

Tom

[Tom OD]

Damn it I m still crashing the Cooler somehow. This was after restarting the PC when it hung the first time tonight.

Any ideas anyone?

This bit seems like I might need to re install the driver or revert to the older Windows version

Property write ASCOM.Atik.Camera SetCCDTemperature is not implemented in this driver. (System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.Runtime.InteropServices.COMException: Property write SetCCDTemperature is not implemented in this driver.

Tom

09/05/19 23:31:54.827][DEBUG] [Telescope Thread] Telescope solve with plate solver PlateSolve2...
[09/05/19 23:31:54.827][DEBUG] [Telescope Thread] Setting filter for scope sync...
[09/05/19 23:31:54.830][DEBUG] [Telescope Thread] Setting filter position 1...
[09/05/19 23:31:54.830][DEBUG] [Telescope Thread] Filter position 1 is already set.  Skipping...
[09/05/19 23:31:54.831][DEBUG] [Telescope Thread] Plate solving scope frame...
[09/05/19 23:31:54.832][DEBUG] [Telescope Thread] Created full file name (file does not exist): C:\Users\PrimaLuceLab\AppData\Local\SequenceGenerator\Temp\plate_solve_image.fit
[09/05/19 23:31:54.837][DEBUG] [Camera Thread] SGM_CAMERA_PLATE_SOLVER_CAPTURE message received...
[09/05/19 23:31:54.838][DEBUG] [Camera Thread] Collecting FITs headers for plate solve frame...
[09/05/19 23:31:54.840][DEBUG] [Camera Thread] Collecting FITs headers for plate solve frame...
[09/05/19 23:31:54.865][DEBUG] [Camera Thread] SetAscomNormalSpeed...
[09/05/19 23:31:54.866][DEBUG] [Camera Thread] Readout speed set to NORMAL...
[09/05/19 23:32:37.111][DEBUG] [PHD2 Listener Thread] PHD2 - No messages received from PHD2 for 1 minute, checking socket with status...
[09/05/19 23:32:37.111][DEBUG] [PHD2 Listener Thread] Checking PHD2 state...
[09/05/19 23:32:37.111][DEBUG] [PHD2 Listener Thread] PHD2 GetPhdStatus - Pre-Wait : Stopped
[09/05/19 23:32:37.111][DEBUG] [PHD2 Listener Thread] Sending to PHD2:
{"method": "get_app_state", "id": 1001}

[09/05/19 23:32:37.111][DEBUG] [PHD2 Listener Thread] PHD2 GetPhdStatus - Post-Wait: Stopped
[09/05/19 23:33:30.459][DEBUG] [TEC Thread] ASCOM Camera: Failed to set CCD Temperature!  : Property write ASCOM.Atik.Camera SetCCDTemperature is not implemented in this driver. (System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.Runtime.InteropServices.COMException: Property write SetCCDTemperature is not implemented in this driver.
   --- End of inner exception stack trace ---
   at System.RuntimeType.InvokeDispMethod(String name, BindingFlags invokeAttr, Object target, Object[] args, Boolean[] byrefModifiers, Int32 culture, String[] namedParameters)
   at System.RuntimeType.InvokeMember(String name, BindingFlags bindingFlags, Binder binder, Object target, Object[] providedArgs, ParameterModifier[] modifiers, CultureInfo culture, String[] namedParams)
   at System.Type.InvokeMember(String name, BindingFlags invokeAttr, Binder binder, Object target, Object[] args, CultureInfo culture)
   at ASCOM.DriverAccess.MemberFactory.CallMember(Int32 memberCode, String memberName, Type[] parameterTypes, Object[] parms) in C:\ASCOM Build\Export\ASCOM.DriverAccess\MemberFactory.cs:line 331)
   at ASCOM.DriverAccess.MemberFactory.CallMember(Int32 memberCode, String memberName, Type[] parameterTypes, Object[] parms) in C:\ASCOM Build\Export\ASCOM.DriverAccess\MemberFactory.cs:line 364
   at ASCOM.DriverAccess.Camera.set_SetCCDTemperature(Double value) in C:\ASCOM Build\Export\ASCOM.DriverAccess\Camera.cs:line 572
   at q9.if(Double A_0, Boolean A_1)
[09/05/19 23:33:30.459][DEBUG] [TEC Thread] TEC Change: Failed to set cooler temp!  Aborting...
[09/05/19 23:33:30.459][DEBUG] [TEC Thread] TEC Change: Aborted...
[09/05/19 23:33:30.464][DEBUG] [TEC Thread] ASCOM Camera: Failed to set CCD Temperature!  : Property write ASCOM.Atik.Camera SetCCDTemperature is not implemented in this driver. (System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.Runtime.InteropServices.COMException: Property write SetCCDTemperature is not implemented in this driver.
   --- End of inner exception stack trace ---
   at System.RuntimeType.InvokeDispMethod(String name, BindingFlags invokeAttr, Object target, Object[] args, Boolean[] byrefModifiers, Int32 culture, String[] namedParameters)
   at System.RuntimeType.InvokeMember(String name, BindingFlags bindingFlags, Binder binder, Object target, Object[] providedArgs, ParameterModifier[] modifiers, CultureInfo culture, String[] namedParams)
   at System.Type.InvokeMember(String name, BindingFlags invokeAttr, Binder binder, Object target, Object[] args, CultureInfo culture)
   at ASCOM.DriverAccess.MemberFactory.CallMember(Int32 memberCode, String memberName, Type[] parameterTypes, Object[] parms) in C:\ASCOM Build\Export\ASCOM.DriverAccess\MemberFactory.cs:line 331)
   at ASCOM.DriverAccess.MemberFactory.CallMember(Int32 memberCode, String memberName, Type[] parameterTypes, Object[] parms) in C:\ASCOM Build\Export\ASCOM.DriverAccess\MemberFactory.cs:line 364
   at ASCOM.DriverAccess.Camera.set_SetCCDTemperature(Double value) in C:\ASCOM Build\Export\ASCOM.DriverAccess\Camera.cs:line 572
   at q9.if(Double A_0, Boolean A_1)
[09/05/19 23:33:30.466][DEBUG] [TEC Thread] SGM_CHANGE_COOLER_TEMP complete...
[09/05/19 23:33:37.220][DEBUG] [PHD2 Listener Thread] PHD2 - No messages received from PHD2 for 1 minute, checking socket with status...
[09/05/19 23:33:37.220][DEBUG] [PHD2 Listener Thread] Checking PHD2 state...
[09/05/19 23:33:37.220][DEBUG] [PHD2 Listener Thread] PHD2 GetPhdStatus - Pre-Wait : Stopped
[09/05/19 23:33:37.220][DEBUG] [PHD2 Listener Thread] Sending to PHD2:
{"method": "get_app_state", "id": 1001}

[09/05/19 23:33:37.220][DEBUG] [PHD2 Listener Thread] PHD2 GetPhdStatus - Post-Wait: Stopped
[09/05/19 23:34:05.635][DEBUG] [Telescope Thread] Scope solve complete...
[09/05/19 23:34:05.802][DEBUG] [Camera Thread] ASCOM Camera: abort message received in download...
[09/05/19 23:34:05.803][DEBUG] [Camera Thread] SGM_CAMERA_PLATE_SOLVER_CAPTURE complete...

[Tom OD]

Looks like it was a USB cable issue. That’s the third in about 5 months now. Same symptoms and same fix. Next time it happens I ll ask Olly to put in one of the old cables in case it was just a dry contact or bad connection issue. 

Tom 

[CedricTheBrave]

I had a similar issue with my Starlight express costar

sometimes tracked ok in phd2 but would lockup and crash the software if i did long single exposures or the deadpixel routine

also sharpcap and the costar software would crash pretty much all the time but Maxim would be fine.

turned out to be a faulty usb chip on the main board of the device

its on its way back to me from Starlight express now so hopefully all sorted

[Davey-T]

Don't know if it's relevant but my Atik 4000 had a problem with the cooler either not cooling or keeping on cooling past the setpoint without stopping, there is an Atik utility that comes with the camera to reset it but didn't work so returned it to Atik for sorting and a service which included cleaning the sensor, not a donut to be seen afterwards 

Dave

[jarbi]

Hi All,

I would like to share the follow-up of this story as far as it goes until now. The lockups of the camera kept happening even after disabling the power saving of the USB ports, and even when I connected the camera on a separate Usb port. I was also trying to revert to the legacy driver from 2018 which worked perfectly last year - no joy.

The camera went for a revision to Atik somewhere in May this year, and I have a bad feeling that these issues started after... 

Finally I bit the bullet and I have sent the camera to Atik again for a hardware investigation a week ago. Hopefully they will come up with something because I am out of ideas...

I will come back here soon when my camera returns, thanks again for everyone for your advises! When it is not a hardware issue it will be a hard nut to crack I am afraid,

 

clear skies,

Janos