#1  
Old 03-02-2016, 01:25 PM
JohnH's Avatar
JohnH
Member # 159

JohnH is offline
 
Join Date: Feb 2005
Location: NSW
Posts: 1,226
ST4000 gone faulty?

Hi SBig users,

I am having problems with my ST4000. I can connect ok but the images are corrupt. I have tried direct connection and a second power supply but it make not difference. I connected my ST2000 to the same cables, PC and power and that worked fine so I am pretty sure it is the camera that has gone faulty. I am attaching a couple examples of what I am seeing and am hoping someone can suggest what the fault might be - and if it is a user fix or a return to SBig job (costly!). I could replace the analog board for example...

Anyway here are the odd images, it seems as if the central part of the chip is not reading/registering photons and the left and right edge areas are active but noisy. I have included a dark frame from better days for comparison. The light frame was a 1 minute exposure indoors with a pinhole in front of the nosepiece. All images are half scale, and stretched to show the issue. It is very odd....
Attached Thumbnails
Click for full-size image (badlight.jpg)
194.4 KB45 views
Click for full-size image (baddark.jpg)
194.0 KB40 views
Click for full-size image (gooddark.jpg)
192.5 KB36 views
Reply With Quote
  #2  
Old 03-02-2016, 10:44 PM
Peter Ward's Avatar
Peter Ward
Galaxy hitchhiking guide

Peter Ward is offline
 
Join Date: Dec 2007
Location: The Shire
Posts: 8,090
Sorry....it needs to go to SBIG 's repair guy.
Reply With Quote
  #3  
Old 07-02-2016, 10:22 AM
JohnH's Avatar
JohnH
Member # 159

JohnH is offline
 
Join Date: Feb 2005
Location: NSW
Posts: 1,226
SBig's advice...

Bill wrote back to me by return...very good service (as always) and pointed the finger at drivers. Well I thought I had eliminated that possibility as the 2k was working ok on the same setup but hey what the heck...so I tried the 4k with CCDOps on a win 7 machine and presto it was fine!

So not a camera fault then.

I realised my error must have been the win 10 upgrade I did a month or so ago on my astroimaging laptop. I had thought to save time by accepting M$ofts option to preserve all my apps and files - then I would just reinstall the things that broke. This was a bad plan. It worked but I did have to re-install CCDSoft and did get the odd error message before the session when the 4k stopped working completely. So I have ended up doing a clean Win10 install and fresh installs of CCDSoft, AstroArt etc. Everything is now functioning as it should (at least as far as a bench test goes). Just need a clear night now to see if it is stable in real conditions but I am hoping the issue was just an old driver conflict or compatibility issue.

Here is the lesson I should not have needed cause I have been there before - if you want to upgrade to Win10 - back up your old machine, do a format and fresh install of everything. Yes you will have more work to do but it is safer and you will end up with a faster and more stable machine at the end. The M$ update might work for a standard office type machine but with the odd bits of software and many non-standard usb devices we have on obs and imaging boxes I think it is likely to let you down.

BTW Win10 has some nasty defaults you may like to disable if you do not want patches and reboots in the middle of an imaging session, Cortona snooping on everything and unwanted adverts fired at you.
Reply With Quote
Reply

Bookmarks

Thread Tools
Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT +10. The time is now 08:29 AM.

Powered by vBulletin Version 3.8.7 | Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Advertisement
Bintel
Advertisement
Testar
Advertisement