View Single Post
  #2  
Old 14-12-2013, 10:46 PM
PRejto's Avatar
PRejto (Peter)
Registered User

PRejto is offline
 
Join Date: Jan 2011
Location: Rylstone, NSW, Australia
Posts: 1,509
Paul,

I would try #3 first. If the problem goes away you are closer to your answer.

A different idea I might put forward is that there have been times that I've had issues with my camera staying connected in TSX CAO. (Different camera though, but these drivers are relatively new and have not matured perhaps). I had better luck with long T-Point runs by connecting my camera to CCDSoft and then picking "CCDSoft camera" in the CAO. (If you try this be sure to check the box on the setup page in the CAO that tells it not to report on the CCD temp. That function seems to eat up a lot of CPU and can bog thins down quite a lot!)

Also, might it be a USB issue from the way you are piping things through the MX USB hub? I've had better luck keeping my imaging camera on a separate USB cable back to the computer rather than sharing the same cable that is running the mount to TSX. I think TSX gets really busy running T-Point and slewing so having the camera with its own dedicated run might make the issue go away.

Hope you get it solved!

Peter
Reply With Quote